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

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

New in Version: 8.1

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


Back to top



Back to top

Sample Request

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

Request URL


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

Sample request body

  "Description":"Swagger Slim Version",

Back to top

Request Headers

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

Header Description

application/json, application/xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml


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

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.

Back to top

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.

Back to top


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

Back to top

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

Back to top

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

Status Code: 200 OK
Content-Type: application/vnd.soa.v81+xml
Date: Fri, 20 May 2016 22:55:03 GMT

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

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<APIImplementationInfo xmlns="http://soa.com/xsd/api/1.0" xmlns:ns2="http://soa.com/xsd/business/1.0" 
xmlns:ns3="http://soa.com/xsd/resource/1.0" xmlns:ns4="http://soa.com/xsd/deploymentzone/1.0" 
xmlns:ns5="http://soa.com/xsd/asset/1.0" xmlns:ns6="http://soa.com/xsd/dnmodel/1.0" xmlns:ns7="http://soa.com/xsd/legals/1.0">

Back to top

Response Headers

For general information on response header values, refer to HTTP Response Headers.

Header Description

application/json, application/xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml

Back to top

Response Body

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

Back to top

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. For example, you might get this if you specified an invalid Accept header or omitted a required Content-Type header, or used the wrong HTTP verb.
500 An error occurred processing the call.

More information about Akana API Platform API error messages.

Back to top

Related Topics