ApiSpecifications
Enter your bearer token in the format Bearer <token>
Current page number. Default value is 1.
Maximum page size is 200. Default page size is 30.
OK
OK
The Base path (openAPI 2) / Server url (openAPI 3) cannot be modified later.
Enter your bearer token in the format Bearer <token>
API specification created
Missing API specification
A path is already used in an existing API
This can be a very slow action. Please make sure your client has a long enough timeout so that the operation does not get cancelled. This creates version 1 of the API specification to the default Agent group. The Base path (openAPI 2) / Server url (openAPI 3) cannot be modified later.
Enter your bearer token in the format Bearer <token>
File to upload.
API specification created
Bad Request
A path is already used in an existing API
Unsupported Media Type
Enter your bearer token in the format Bearer <token>
API specification identifier
OK
API specification not found
Enter your bearer token in the format Bearer <token>
API specification identifier
OK
Bad Request
API specification not found
No content
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
OK
API specification or version not found
To delete a specification from the default Agent group, it must first be deleted from all other Agent groups. Deleting the API specification from the default Agent group deletes it permanently. Linked processes are not deleted.
Enter your bearer token in the format Bearer <token>
API specification identifier
Agent Group identifier
API specification deleted successfully
Could not find the requested API specification or Agent Group
Could not delete the API specification from the default Agent group, because it is deployed to another Agent Group
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
The path of the HTTP endpoint, as specified in the API specification
The operation of the endpoint (e.g. GET)
OK
Bad Request
API specification or version not found
This locks down the current specification and process versions. A new active version is created, and the previous one becomes deployable.
Enter your bearer token in the format Bearer <token>
API specification identifier
Description of the changes made
API specification published
API specification not found
The current state of linked processes is not fit for publishing
No content
Returns information about the processes which must be deployed to finish the API deployment. The processes can be deployed using the process-deployments API.
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
Agent Group identifier
Deployment started
Bad Request
API specification, version or Agent group not found
No content
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
OK
API version not found
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
Is CORS enabled
Allowed origins. Used when CORS is enabled.
Source API path for this passthrough configuration. Not used when IsDefault is set to true.
HTTP method. Not used when IsDefault is set to true.
Is this configuration used for all paths and HTTP methods
API passthrough configuration created
No content
Invalid API passthrough configuration
API version not found
A path is already used in an existing API
No content
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
API passthrough configuration identifier
Is CORS enabled
Allowed origins. Used when CORS is enabled.
OK
Bad Request
API version or passthrough configuration not found
Enter your bearer token in the format Bearer <token>
API specification identifier
API specification version
API passthrough configuration identifier
API passthrough configuration deleted successfully
API version or passthrough configuration not found
No content
Was this helpful?

