2 min read
Endpoint
| Method | GET |
| Path | /partner/v1/* |
| Ring | partner (list conventions) |
| Auth | OAuth |
Request
List endpoints accept a limit and a cursor. The response carries the page of items plus a next_cursor when more remain.
Response
Partner collections use cursor pagination. Pass limit for the page size and, on each subsequent call, the next_cursor from the previous response. When next_cursor is absent or null, you have reached the end. Cursor paging is stable under concurrent inserts, unlike offset paging, so you never skip or repeat an item mid-iteration.
Errors & notes
Do not construct cursors yourself — treat them as opaque. A 400 for a malformed cursor. Reads count against your bucket, so page at a reasonable size rather than one item at a time.
Frequently asked questions
Why cursor pagination instead of page numbers?
Cursors are stable when rows are inserted during your iteration — you never skip or double-read an item. Offset/page-number paging can shift under concurrent writes.
Can I build my own cursor?
No. Cursors are opaque tokens — pass back exactly what the previous response returned. Constructing one yourself returns a 400.
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 →
Partner API error reference
The error model for the /partner/v1 ring: auth errors, scope errors, validation, conflict, the 429 with…
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.