™2 min read
What it is
Idempotency means that making the same request more than once has the same effect as making it once. Reading a resource is naturally idempotent — fetching the loyalty tiers twice changes nothing. This is why safe retries are fine for the public ring’s GET endpoints.
On the public ring
Every public GET — loyalty tiers, CMS pages, billers, the MCP server card — is idempotent, so retrying after a network blip or a 429 is safe. The write endpoints (enquiries, consent) are one-shot submissions: only retry them when you are sure the first attempt did not reach the server (for example, a connection error before any response), to avoid recording a duplicate.
Frequently asked questions
Is it safe to retry an enquiry POST?
Only if you are confident the first attempt never reached the server. A POST is not idempotent, so a blind retry can record a duplicate. Reads are always safe to retry.
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.