2 min read
Endpoint
| Method | POST |
| Path | /partner/v1/decisions/{id}/refresh |
| Ring | partner (OAuth) |
| Auth | OAuth |
Request
Path parameter id. An optional body carrying updated inputs. Requires decisions:write. Send an Idempotency-Key.
Response
A response indicating a refresh was queued; the new outcome arrives via the decision webhook or a subsequent read. Refresh re-runs the model, which is expensive — do it only when materially new information (updated financials, a corrected figure) would change the result, not speculatively.
Errors & notes
Sub-limited to 1 req/s — re-running the model is costly. A 409 if a refresh is already in flight; a 403 without decisions:write. Idempotency applies.
Frequently asked questions
When should I refresh a decision?
Only when genuinely new information would change the outcome — updated accounts, a corrected amount. Refreshing speculatively wastes the 1 req/s sub-limit and the model run for no benefit.
Why is refresh limited to 1 req/s?
Each refresh re-runs the decisioning model, which is the most expensive operation on the ring. The tight sub-limit keeps that cost bounded.
Related reading
GET /partner/v1/decisions/{id}
Read a credit decision on the partner ring: the outcome, any conditions and the offer terms. Decisioning is…
Read →
POST /partner/v1/applications
Open a new application on the partner ring. Idempotent with an Idempotency-Key, scoped to applications:write,…
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.