View deployed API definition
/apiplatform/management/v1/apis/{apiId}/deployments/{depId}/api
Returns the runtime definition of the {depId}
deployment of the {apiId}
API.
Users requesting this resource must be assigned the Plan Manager, API Manager, or Gateway Manager roles and must be issued the Manage API or View All Details grant for the specified API.
Request
- application/json
-
apiId: string
A unique ID referencing a specific API.
-
depId: string
A unique ID referencing a specific deployment.
Response
- application/json
200 Response
403 Response
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
500 Response
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
Examples
The following example shows how to retrieve the runtime definition of the deployment by submitting a GET request on the REST resource using cURL. For more information about cURL, see Use cURL
curl -i -X GET
-H "Authorization: Bearer access_token"
https://example.com/apiplatform/management/v1/apis/{apiId}/deployments/{depId}/api
-
{apiId}
is the unique ID for an API. To retrieve available API IDs, see Get APIs. -
{depId}
is the unique ID for a deployment. To retrieve available deployment IDs, see Get API deployments.
Example of Response Headers
The following shows an example of the response headers.
HTTP/1.1 200 OK Date: Fri, 17 Mar 2017 07:31:31 GMT Server: Oracle-Traffic-Director/12.2.1.0.0 Content-Length: 522 Content-Type: application/json X-oracle-dms-ecid: f102c33f-1c5b-4409-806d-03bf5706c492-0002af4a X-oracle-dms-rid: 0 Via: 1.1 otd_opc Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0
Example of Response Body
The following example shows the contents of the response body in JSON format, including the ID, name, version, and iteration of the deployment.
{ "implementation": { "executions": { "request": [ "1", "2" ], "response": [ "3", "4" ] }, "policies": [ { "draft": false, "id": "1", "type": "o:ApiRequest", "version": "1.0", "config": { "protocols": [ "HTTP" ], "url": "exampleEndpoint" } }, { "draft": false, "id": "2", "type": "o:ServiceRequest", "version": "1.0", "config": { "useProxy": true, "url": "http://www.example.com" } }, { "id": "3", "type": "o:ServiceResponse", "version": "1.0", "config": {} }, { "id": "4", "type": "o:ApiResponse", "version": "1.0", "config": {} } ] }, "name": "john test", "id": "103", "iterationId": "3", "version": "1" }