You can use the swagger console to test all the APIs. Please make sure you are using the right environment. If you are building a marketplace app, your app should be approved and live in the staging or production environments before you can test it.
If your app is not live (you cannot see it in the marketplace) you can contact [email protected].
Make sure you have got the correct credentials and they are included in the request's header. All API calls need to have the header set.
For simplicity, we have removed all the authentication headers in this documentation. And they are explained in the Credentials section.
All error responses are following the below structure:
{"error": {"code": "number","title": "string","message": "string","status": "number","reason": "string"}}
Property | Type | Description |
| number | ​Error Code​ |
| string | Title of the occurred error. |
| string | A message which describes why the error has happened. |
| number | HTTP status code. |
| string | Reason of the error (optional). |
{"error": {"code": 6,"title": "ALREADY_EXISTS","message": "This document already exists","status": 409,"reason": "pmsNumberIsDuplicate"}}
CANCELLED = 1UNKNOWN = 2INVALID_ARGUMENT = 3DEADLINE_EXCEEDED = 4NOT_FOUND = 5ALREADY_EXISTS = 6PERMISSION_DENIED = 7RESOURCE_EXHAUSTED = 8FAILED_PRECONDITION = 9ABORTED = 10OUT_OF_RANGE = 11UNIMPLEMENTED = 12INTERNAL = 13UNAVAILABLE = 14DATA_LOSS = 15UNAUTHORIZED = 16METHOD_NOT_ALLOWED = 17NOT_ACCEPTABLE = 18
There are some errors that are common between all APIs.
When your provided authentication tokens are wrong, you will get the following error
{"error": {"code": 16,"title": "UNAUTHORIZED","status": 401,"message": "valid credential required","reason": "invalidCredentials"}}
When your provided data is wrong (you missed a required field or type of a field is not match with what the API expects) you will get a validation error.
{"error": {"code": 3,"title": "INVALID_ARGUMENT","status": 400,"message": "A message which describes the error."}}