CreditcorpDev
Public API

Choosing the right endpoint

Not sure which public endpoint you need? Start here. This guide maps common goals to the right endpoint — reading products, showing the loyalty ladder, taking a contact enquiry, recording cookie consent, embedding support chat, or connecting an AI agent — so you pick the shortest path to what you want.

2 min read

goal → endpointDecision guide
publicRing scope
shortest pathWhat to call

I want to show product info

For a human page, read the product pages or use the CMS endpoint for published copy. For an AI agent, use the ListProducts and ProductDetails MCP tools.

I want to show the loyalty ladder

Read GET /public/v1/loyalty/tiers and cache it. See render the ladder.

I want to take a contact enquiry

Post to POST /public/v1/enquiries with a consent flag. See submit a contact form.

Forward from your edge to POST /public/v1/consent. See record cookie consent.

I want live chat

Embed the support widget. See embed the widget.

I want an AI agent to answer accurately

Connect it to the MCP server. See connect an agent.

Frequently asked questions

Should I use REST or MCP for product data?

REST (or the product pages) for a human-facing page; MCP when an AI agent is the consumer and you want it to discover and call the data as a tool.

What if none of these fit my goal?

You may need the authenticated partner API. Anything per-customer or money-moving is not on the public ring — see moving to the partner API.

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.

Explore business loans Apply now