POST /api/businesses/{BusinessID}/resources
Adds a scope on the platform.
Authorization Roles/Permissions: Must be logged in. Must have Add permission for the resource. Site Admin or Business Admin.
This topic includes the following sections:
HTTP Method
POST
URL
https://{hostname}/api/businesses/{BusinessID}/resources
Sample Request
The example below shows a request to add a scope.
Sample Request URL
https://{hostname}/api/businesses/tenantbusiness.acmepaymentscorp/resources
Sample request headers
POST /api/businesses/tenantbusiness.acmepaymentscorp/resources HTTP/1.1 Host: {hostname} Accept: application/json, text/javascript, */*; q=0.01 Content-Type: application/json X-Csrf-Token_acmepaymentscorp: TokenID%3D8ed70a13-8469-11e8-b37a-b155e4eabeb8%2CexpirationTime%3D153...
Sample request body
{ "ResourceID":"", "Name":"Bronze access", "ShortDescription":"Bronze access", "LongDescription":"Bronze access", "Visibility":"Public", "SandboxAnonymousAccessAllowed":"false", "ProductionAnonymousAccessAllowed":"false", "ResourcePath":"", "OAuthGrantDefaultResource":"true", "OAuthGrantUserAuthorizationRequired":"true", "ParentResourceID":"", "BusinessID":"tenantbusiness.acmepaymentscorp" }
Request Headers
For general information on request header values, refer to HTTP Request Headers.
Header | Description |
---|---|
Accept | application/json, application/xml, application/vnd.soa.v71+json, application/vnd.soa.v71+xml, application/vnd.soa.v72+json, application/vnd.soa.v72+xml, application/vnd.soa.v80+json, application/vnd.soa.v80+xml, application/vnd.soa.v81+json, application/vnd.soa.v81+xml |
Content-Type |
Any one of the following media types is valid for the request Content-Type: application/json or application/xml application/vnd.soa.v71+json or application/vnd.soa.v71+xml application/vnd.soa.v72+json or application/vnd.soa.v72+xml application/vnd.soa.v80+json or application/vnd.soa.v80+xml application/vnd.soa.v81+json or application/vnd.soa.v81+xml |
Cookie | AtmoAuthToken_{fedmemberid}={cookie value, which usually starts with TokenID}—The platform cookie. This is the Akana API Platform authorization token, and must be sent with every API request that requires login. For more information and an example, see Session cookies. |
X-Csrf-Token_{fedmemberID} | The CSRF prevention header; may or may not be required, depending on platform settings. See CSRF Prevention on the Platform. By default, the CSRF header is not required for GET operations and is required for all others, with a few exceptions relating to user login. |
Request Parameters
Parameter | Parm Type | Data Type | Required | Description |
---|---|---|---|---|
BusinessID | Path | string | Required | The unique ID for a specific business organization on the platform. |
Resource | Body | Resource | Required |
Contains information about a resource, such as a scope, defined for a business organization. The unique ID is the Name field. |
Response
If successful, this operation returns HTTP status code 200, with information about the scope that was added.
Sample Response
The sample response below shows successful completion of this operation.
Sample response headers: application/json
HTTP/1.1 200 OK Date: Fri, 07 Oct 2016 20:22:18 GMT Content-Type: application/json
Sample response body: application/json
{ "ResourceID" : "74e58bdd-0c5a-47f9-b141-cbaa83e64293.acmepaymentscorp", "Name" : "Access to READ operations", "ShortDescription" : "Access to READ operations", "LongDescription" : "Access to READ operations", "Visibility" : "Public", "SandboxAnonymousAccessAllowed" : false, "ProductionAnonymousAccessAllowed" : false, "ResourcePath" : "", "OAuthGrantDefaultResource" : true, "OAuthGrantUserAuthorizationRequired" : true, "BusinessID" : "tenantbusiness.acmepaymentscorp" }
Response Headers
For general information on response header values, refer to HTTP Response Headers.
Header | Description |
---|---|
Content-Type | application/json, application/xml, application/vnd.soa.v71+json, application/vnd.soa.v71+xml, application/vnd.soa.v72+json, application/vnd.soa.v72+xml, application/vnd.soa.v80+json, application/vnd.soa.v80+xml, application/vnd.soa.v81+json, application/vnd.soa.v81+xml |
Response Body
Name | Type | Description |
---|---|---|
Resource | Resource | Contains information about a resource, such as a scope, defined for a business organization. |
Error Codes/Messages
If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.
Item | Value |
---|---|
401 | Unauthorized. For example, you would get this response if you didn't include the custom X-Csrf-Token_{fedmemberID} header in the request, when it was required by the platform settings; or if you included an invalid or expired value for this header. You would also get this response for any operation that requires login (almost all) if the login cookie was missing. |
500 | An error occurred processing the call. |
More information about Akana API Platform API error messages.