Public API

Data you can read vs submit

The public ring is easy to reason about once you split it into reads, submits and off-limits. You can read public vocabulary — products, tiers, published pages, billers — and submit two safe things — enquiries and cookie consent. Everything per-customer or money-moving is off-limits and lives behind authentication.

2 min read

readPublic vocabulary
submitEnquiries + consent
off-limitsAccounts + money

What you can read

The loyalty ladder, published CMS pages, the Slice biller registry, and — via MCP — products, quotes, eligibility and how-to-apply. All public, all keyless, all cacheable.

What you can submit

Two things: a contact/department enquiry (with mandatory consent) and a cookie-consent snapshot. Both are validated and safe to accept from the open internet.

What is off-limits

Reading a specific customer’s account, creating or accepting offers, moving money, running a real credit decision — none of these appear on the public ring. They require authentication. See moving to the partner API.

Frequently asked questions

Can I read a customer’s loan balance?

No. No per-customer data is on the public ring. Account-level reads require authentication on the partner/internal surface.

Can I submit a loan application?

No. Applications are off-limits on the public ring. The MCP HowToApply tool can explain the steps, but the application itself is authenticated.

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.