™2 min read
Test the reads live
Loyalty tiers, CMS pages and billers change nothing and carry no PII — assert on their shapes directly against the live endpoint. Check the status is 200, the expected fields exist, and the generated timestamp is recent.
Handle writes carefully
Enquiries and consent record real data. Use obvious test values (a clearly fake company name, a role-based test email), assert on the 201, and do not run write tests in a tight loop. See sandbox.
Assert on codes, not messages
Branch tests on the HTTP status and the error code, which are stable. Do not assert on the human message — it may be reworded.
Respect the limit
Keep your test run under 60 requests per 60 seconds per IP, or expect a 429. Add a small delay between tests if you have many. See rate limits.
Frequently asked questions
Is there a dedicated sandbox for the public ring?
The reads are safe to test live. For a full partner sandbox with test data, see the partner sandbox docs. On the public ring, use clear test values for writes.
What should my tests assert on?
HTTP status and the stable error code, plus the presence of expected fields. Do not assert on the human-readable message.
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.