Let's start lending! 🚀
Day 1 guide to starting digital lending on the Apollo Platform
Here’s a collection of APIs that are fundamental to digital lending on the Apollo Platform. This is the rock-solid foundation on which 40+ companies have embarked on their lending journey 🌈
Start your engines. You are now 48 hours away from doing your first digital loan! 🚀
All our APIs are organized around REST*. Our APIs have predictable resource-oriented URLs, accept form-encoded** request bodies, return JSON encoded** responses, and use standard HTTP response codes.
If the tech jargon is lost on you:
*Here is a quick explainer video on REST APIs
**Think of form-encoded as an acceptable format to post a request in.
It’s simple to integrate, brilliantly documented, and most importantly suited to match your tech team’s ever-limited bandwidth
For ease of testing, we have distinct test and live environments. Switching over from test to live is easy: Simply change the URL and the unique key allocated by Apollo Finvest to production credentials and boom, you're live!
To make this Day 1 guide crisp, we have hand-picked a few core APIs out of our larger bouquet of 20+ APIs and split them into 5 broad categories as mentioned below.
We have integrations with leading players in the KYC automation space (Karza & HyperVerge). Their entire gamut of services are available with us
The credit API can be chosen depending on the underlying raw credit bureau data on which the credit score is built
Loan Creation API:
This API is used to pass approved borrower personal data, loan data, KYC documents, and Loan Agreement through a single API to create loans on Sonic
We have made disbursement updates proactive and efficient. To know the status of the disbursements you can use our Webhook API
We have integrations with multiple payment gateways like RazorPay, Cashfree, PayU, etc. to enable different modes of collections
All our API Responses are communicated via HTTP using following the status codes :
200 - OK
Everything worked as expected
400 - Bad Request
The request was unacceptable, often due to missing a required parameter
401 - Unauthorized
No valid API key provided
402 - Request Failed
The parameters were valid but the request failed
403 - Forbidden
The API key doesn't have permissions to perform the request
404 - Not Found
The requested resource doesn't exist
409 - Conflict
The request conflicts with another request (perhaps due to using the same idempotent key
429 - Too Many Requests
Too many requests hit the API too quickly. We recommend an exponential backoff of your requests
500, 502, 503, 504 - Server Errors
Something went wrong at our end- Very Rare!
How can Fintechs get started with testing? 🚀
Write to us at firstname.lastname@example.org
We will share the postman collection containing these APIs for a quick trial
Let the magic begin! ✨