PUT /api/apis/versions/{APIVersionID}/implementations/{ImplCode}/info

Updates information about the specified implementation for the specified API version.

Authorization Roles/Permissions: Must be logged in. Must have permission to modify the API; an API Admin or Business Admin.

This topic includes the following sections:

HTTP Method

PUT

URL

https://{hostname}/api/apis/versions/{APIVersionID}/implementations/{ImplCode}/info

Sample Request

The example below shows a request to modify the API implementation information to remove anonymous access from the Sandbox implementation.

Sample Request URL

https://{hostname}/api/apis/versions/f7f250fc-8405-43e0-9073-0f56a918d676.acmepaymentscorp/implementations/Sandbox/info

Sample request headers

PUT /api/apis/versions/f7f250fc-8405-43e0-9073-0f56a918d676.acmepaymentscorp/implementations/Sandbox/info HTTP/1.1
Host: acmepaymentscorp.com
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

{
  "AnonymousAccessAllowed":false,
  "EndpointAccessAutoApproved":true,
  "Description":"Swagger Slim Version",
  "Pattern":"com.akana.pattern.proxy"
}

Request Headers

For general information on request header values, refer to HTTP Request Headers.

Header	Description
Accept	application/json, application/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.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
APIVersionID	Path	String	Required	The unique ID for a specific API version.
ImplCode	Path	String	Required	A code for a specific implementation. Valid values: Live or Sandbox.
APIImplementationInfo	Body	APIImplementationInfo	Required	Contains information about an API implementation.

Response

If successful, this operation returns HTTP status code 200, with the updated implementation information.

Sample Response

The sample response below shows successful completion of this operation.

Sample response headers: application/vnd.soa.v81+json

HTTP/1.1 200 OK
Date: Fri, 20 May 2016 22:54:09 GMT
Content-Type: application/vnd.soa.v81+json

Sample response body: application/vnd.soa.v81+json

{
  "APIVersionID" : "f10624ed-9a23-4cb9-90d4-595d4a7c64f9.acmepaymentscorp",
  "ImplementationCode" : "Sandbox",
  "Pattern" : "com.akana.pattern.proxy",
  "ServiceKey" : "uddi:e4f16dc7-1eda-11e6-a076-bde7b81dff00",
  "AnonymousAccessAllowed" : false,
  "EndpointAccessAutoApproved" : true,
  "APIOwnedImplementation" : true
}

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.v81+json, application/vnd.soa.v81+xml

Response Body

Name	Type	Description
APIImplementationInfo	APIImplementationInfo	Contains information about an API implementation.

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.
405	Method Not Allowed. You might get this if there is an error in the URL, or if you used the wrong HTTP verb.
500	An error occurred processing the call.

More information about Akana API Platform API error messages.

Related Topics