Sandbox APIs, in some cases, act as a bridge and use third-party APIs to pull data that has been requested by our service client(eg. in case of Compliance APIs, etc.). This is only possible using third parties which is why Quicko helps its clients get access to this data by creating a bridge between the client and the respective third party.
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 an 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 set up cost, Onboarding/ application fees to the source party as Quicko pays for it as an add-on benefit for its customers.
While Business APIs are free to use with the subscription, an additional cost may be incurred for Compliance APIs. Once you subscribe to our service you can also access these third-party APIs through us. We have done all the groundwork of tying up with multiple institutes in order to provide resilience & fault tolerance. However, when we call these third-party APIs a cost is incurred for APIs called. We ensure that the price you pay to Quicko for these API calls is the same as what you would pay to the source directly. Read more here
Paid API Charges
Invalid Headers or Query/Path Params
Invalid API Key/Secret
Invalid/Expired Authorization Header
Invalid Request Body
Too many requests
Internal Server Error
Errors in Sandbox Services