Overview
Apps consuming your API seldom fail because the server is down; far more often a field becomes optional or changes type without warning. Our suite holds every response up against its expected schema, looks at status codes and the format of errors, and exercises the access rules that stop one customer from seeing another's data. Because it runs against each pull request, any breaking change turns your pipeline red before a partner ever raises a complaint. You also get snapshots of each schema, making accidental changes visible in code review.
What you receive
- Up to 40 endpoints covered by contract tests validated against schemas
- Checks on status codes, headers and error format for every endpoint
- Access tests confirming role limits and per-record permissions are enforced
- Negative tests sending malformed bodies and leaving out required fields
- Pipeline step that reports exactly which contract a change has broken
- Stored schema snapshots so unexpected changes show clearly in diffs
- Short guide on adding tests whenever a new endpoint ships
How it runs
-
Step - 01
Catalogue
We list every endpoint in scope and record its current response formats.
-
Step - 02
Confirm
Your engineers confirm intended behaviour and we flag any gaps or surprises.
-
Step - 03
Write
Tests are built per endpoint, including access control and malformed-input cases.
-
Step - 04
Integrate
The suite joins your pipeline and we prove it with a deliberate breaking change.
Timeline: 9 working days, counted from the day we receive what we need from you.
Is it a fit?
A good match for
- Teams whose shipped mobile app struggles to keep up with server changes
- Products with an API that external partners build against
- Back ends that nobody dares to refactor for fear of side effects
What we need from you
- API access, with a set of credentials for every user role
- Any machine-readable API specification you have, though it is optional
- An engineer who can settle the correct response whenever behaviour looks ambiguous
Why it helps
- Breaking changes turn the pipeline red before any user notices
- Refactoring becomes safer once contracts are checked automatically
- Mobile releases already in the field stop crashing when the server evolves
Questions
Unit tests exercise internal logic inside your code. Contract tests check the outward promise your API makes about response shape, status codes and access, which is what consuming apps and partners actually depend on.
No. Without one, we record how your endpoints behave today and confirm with your engineers which behaviour is intended. This often brings a few surprising responses to light.
Yes. We apply the same approach using schema checks and assertions at the query level, within the same limit of up to 40 endpoints and at the same price.