For partner engineering teams
The Partner API
Hand over cases, track what happened to each one, and receive receipts — without anyone emailing a spreadsheet. The full reference, schemas and sandbox live on the developer portal.
Three things worth knowing before you read the docs
HMAC request signing
Every request carries a signature over the body and a timestamp. There's no OAuth dance — no token store to run, no refresh loop to debug, and a leaked URL is worth nothing on its own.
Signed webhooks
Status changes and receipts are pushed to your endpoint, signed the same way as requests and safe to replay. Verify the signature, ack, and move on.
Sandbox before signature
Read the reference and build against sandbox data without a commercial agreement in place. Production credentials are issued during partner onboarding.
What you can do with it
The API covers the collections lifecycle for cases you hand to Quikkred. Request and response schemas, error codes and rate limits are documented in full on the portal.
developers.quikkred.in- —Push overdue cases to us as they age into a bucket, or let us pull them from your endpoint
- —Read allocation and field-visit status for any case you've handed over
- —Pull receipts and dispositions for reconciliation against your own ledger
- —Subscribe to webhooks instead of polling for changes
Credentials come with onboarding
Read the docs and build against sandbox whenever you like. To get production keys, your organisation files a partner application — licence details, one business contact, one technical contact. Reviewed within two business days.
Apply to partner