Some of the Sandbox APIs are termed as Paid APIs that have an additional upstream charge associated with them.
In such cases, Sandbox acts as a bridge and uses third-party APIs to pull data that has been requested by our service client (eg. in the case of Compliance APIs, etc.). Pulling such data is only possible by using third parties.
We recommend you continue using Sandbox APIs to access this third party data for the following reasons:
We have already spent time on understanding these third-party APIs, Private key infrastructure, and created integrations, ensuring our customer does not have to go through the hassle
We provide easy self-served Onboarding, seamless API integration, simple subscription plans, well-defined API docs, and a better UI/UX suitable for our clients
We do not charge over and above the cost, we incur from these third parties, therefore you get access to this data at the same cost as you would if you were to approach the source directly.
Sandbox APIs ensure immediate access to this data with easy to use RESTful APIs
You do not have to pay the one-time setup cost, Onboarding/ application fees to the source party as Quicko pays for it as an add-on benefit for its customers.
Paid APIs have additional upstream charges associated with them.
Calling these third-party APIs a cost is incurred for APIs called. We ensure that the price you pay to Sandbox for these API calls is the same as what you would pay to the source directly.
Read more here
|Status Code||Description||Notes||Quota||Paid API Charges|
|Bad Request||Invalid Headers or Query/Path Param||No||No|
|Unauthorized||Invalid API Key/Secret||No||No|
|Forbidden||Invalid/Expired Authorization Header||No||No|
|Unprocessable Entity||Invalid Request Body||Yes||No|
|Too many requests||Quota Exhausted||No||No|
|Internal Server Error||Errors in Sandbox Services||No||No|
|Service Unavailable||Source Unavailable||No||No|
|Gateway timeout||Request timeout||No||No|
Updated 5 months ago