2 min read
Reads carry no customer data
Every public read — products, pricing, quotes, loyalty, MCP — returns only published, non-sensitive figures. There is no customer record on this ring, which is exactly why it needs no authentication and is safe to cache.
The two writes are special
Enquiries and consent do record real data — a lead and a PECR consent snapshot. Both require the visitor's consent, both are fail-open, and neither returns stored data to the caller. Treat the data you send them with the same care in development as in production.
Where customer data actually lives
Anything customer-specific — a borrower's own loan, tier or history — is behind authentication on the partner ring or in the portal, never on the public ring. If you need customer data, you need partner access and the customer's authorised context.
Frequently asked questions
Does the public API ever return customer data?
No. Reads return only published figures. The two write endpoints record a lead and a consent choice but return nothing customer-specific. All customer data is behind authentication elsewhere.
Do the write endpoints need consent?
Yes. Both enquiries and consent require the visitor's consent, in line with PECR/GDPR. They are also fail-open, so the visitor's journey is never blocked by a storage failure.
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.