Quickstart

Quickstart: Understand webhooks: public vs partner

The public ring is request/response only; webhooks live on the authenticated partner ring, because event callbacks carry account data. This recipe shows the exact code, uses only the unauthenticated public ring, and links out to the endpoints and the application flow so the reader always has a next step.

2 min read

no webhooksOn the public ring
partnerWhere callbacks live
pollPublic fallback

Why the public ring has no webhooks

Webhooks push account-specific events — a decision, a payment — to your server. Those events belong to an authenticated relationship, so they are delivered on the partner ring, not the anonymous public ring.

What to do on the public ring

For public-ring integrations you drive the interaction: submit an enquiry and follow the handoff_url. If you need event callbacks, that is the signal to onboard to the partner programme.

Polling as a stopgap

Where you only need to know whether reference data changed, poll politely with conditional requests rather than expecting a push.

Frequently asked questions

Can I get a webhook when an enquiry converts?

Not on the public ring. Conversion and decision events are delivered on the partner ring, which requires onboarding and authentication.

How do I move to the partner ring?

Apply through the partner programme documented on the developer portal. It gives you OAuth2 credentials, webhooks and the write endpoints.

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.