2 min read
Endpoint
| Method | POST |
| Path | /partner/v1/applications |
| Ring | partner (OAuth) |
| Auth | OAuth |
Request
A JSON application body (company details, requested amount and term, the product). Send an Idempotency-Key header so a retry cannot open a duplicate case. Requires the applications:write scope.
Response
A 201 with the created application's id and initial status. The decision is produced asynchronously — read it at GET /partner/v1/decisions/{id} or, better, subscribe to a decision webhook. A replay carrying the same idempotency key returns the original 201, not a second case.
Errors & notes
This endpoint carries a tighter 5 req/s sub-limit — each call opens a decisioning case. A 422 for an invalid body (see the partner errors); a 403 if your token lacks applications:write. Always send an idempotency key.
Frequently asked questions
Why is this endpoint limited to 5 req/s?
Because each call opens a decisioning case, which is expensive. The sub-limit protects the model and your own downstream. Batch responsibly and rely on webhooks rather than tight polling.
How do I avoid duplicate applications?
Send an Idempotency-Key header. A retry with the same key returns the original application instead of opening a second case, so a timeout-driven retry is safe.
Related reading
GET /partner/v1/applications/{id}
Read a single application's current state on the partner ring: its status, the submitted details and links to…
Read →
GET /partner/v1/decisions/{id}
Read a credit decision on the partner ring: the outcome, any conditions and the offer terms. Decisioning is…
Read →Funding for UK limited companies
Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.