Public API vs partner API: which one do you

A one-question test

Ask one thing: does what you are building touch a customer, a credit decision or a payment? If the answer is no — you are rendering a quote, showing the product ladder, listing loyalty tiers, or answering questions via an agent — the public ring is all you need, and you can start today without applying for anything. If the answer is yes, you need a partner project and an OAuth credential.

Side by side

Concern	public/v1	partner/v1
Auth	None (reads)	OAuth 2.0 client credentials
Rate limit	60 req / 60s per IP	Token-bucket, scales with tier
Data	Published figures only	Customer + decision + payment data
Writes	Enquiries + consent only	Applications, payments, identity checks
Sandbox	None	Independent sandbox project
Where to start	Call it now	Request access, then OAuth

You can use both

Most integrations that go live use both rings. A comparison platform, for example, might render live quotes from the public quote endpoint on its results page, then hand qualified users into the token-gated application flow on partner/v1. The public ring is your shop window; the partner ring is your till.

Frequently asked questions

Can I move money on the public ring?

No. Anything that moves money is on the token-gated partner/v1 ring, and money-out specifically is Credicorp's single manual gate. The public ring publishes figures and accepts leads and consent only.

Is the public ring cheaper than partner access?

The public ring is free and needs no account. Partner access is priced by tier — see the partner programme — but the rings serve different jobs, so it is not really a cost comparison. Use the public ring for what it covers and the partner ring for the rest.