Browse the Knowledge Hub211 resources
An API checklist to run per endpoint, not per project
Contract and schema, input validation, authentication and object level authorisation, error behaviour, security, performance and asynchronous flows. Every check states why it earns its place, and the ones that should block a release are flagged.
Last updated
- checks
- 34
- groups
- 6
- blocking items
- 9
- CSV download
- Free
Checklist
All 34 checks, grouped by when they apply
Free to use and adapt, no sign-up. Download as CSV or Markdown, or copy it straight into your own tooling.
0 of 34 complete
Ticking is local to your browser and is not saved or sent anywhere.
Contract and response shape
Run these for every endpoint. Structural drift is what silently breaks consumers.
Input validation
Authentication and authorisation
Errors and edge behaviour
Security and transport
Performance and integration
How To Use This
Work it per endpoint, not once per release
API coverage gaps form endpoint by endpoint. One gets the full treatment, the next gets a status code check and ships.
Authorisation on every endpoint
The object level authorisation check is the highest-value item here. Run it on every route that takes an identifier, including exports.
Automate the repeatable parts
Schema validation, status codes and auth negatives belong in the pipeline. Reserve manual effort for the scenario work.
Stub what you cannot break
A provider will not return a 500 on demand. Stubbing is the only way to verify your retry and fallback behaviour.
Test the errors as a contract
Error shape, codes and leakage are part of the API contract. Consumers depend on them as much as the success path.
Why These Checks
The four checks that catch the most serious defects
Object level authorisation is first for a reason. Authenticate as one user, capture a resource identifier, then request it as another and confirm you are refused. It takes a minute per endpoint, it is rarely done systematically, and it is the top entry on the OWASP API Security list. With sequential identifiers it turns from a single-record leak into mass data exposure.
Idempotency is second. Networks retry, clients double-submit, and gateways time out after the work has already been done. Without an idempotency key or equivalent, a retried charge becomes a duplicate charge, which is the single worst defect class in any payment integration.
Schema validation is third, because it is the only check that catches structural drift. Field-by-field assertions verify what you thought to check; a schema catches a field silently changing type, becoming optional, or disappearing, which is exactly what breaks downstream consumers without breaking your tests.
Error leakage is fourth and the easiest to fix. Stack traces, SQL fragments and internal hostnames in an error response are free reconnaissance, and they usually appear because verbose error handling added during development was never turned off for the deployed environment.
Suggest an improvementNeed API coverage built?
QAble builds API and contract test suites that run in your pipeline, including the authorisation and idempotency checks most teams skip.
API testing servicesTemplates & Checklists
More templates and checklists
Test case template
Template12 fields with worked examples from a real authentication feature, plus guidance on what belongs in each column. CSV for Excel and Sheets.Test plan template
Template10 sections with per-section guidance and filled examples from a real release, trimmed from IEEE 829 to the parts that change a decision.Bug report template
TemplateA defect format that shortens developer triage, with worked examples and the fields that stop a report bouncing back.QA release checklist
ChecklistPre-release gates across functional, regression, performance, security, accessibility and rollback readiness.Mobile app testing checklist
ChecklistDevice, network, permission, lifecycle and store-readiness checks for iOS and Android releases.Regression testing checklist
ChecklistHow to scope a regression pass by impact instead of running everything, with the areas teams most often miss.Also free
Tools that run in your browser
Free, no sign-up, and nothing you enter is uploaded.
- JSON compare Compare two JSON documents or API responses by structure: key order ignored, arrays aligned, and the fields you choose skipped. Every difference with its exact path.
- JSON Schema generator Turn JSON samples or API responses into a draft 2020-12 or draft-07 schema with nullable fields, required keys and formats, then validate any JSON against it.
- CURL converter Convert a curl command to Python requests, JavaScript fetch, or an API test in Playwright, Cypress, REST Assured or k6, with secrets moved to environment variables.
Sources
Where the facts come from
- RFC 9110: HTTP Semantics authoritative definition of methods, status codes and conditional requests.
- OWASP ASVS verification requirements for authentication, session and access control.
- OWASP Top 10 the risk categories these security cases map to.
Want your API tested properly, not just checked for 200s?
QAble builds API test suites with ISTQB-certified engineers. Start with a free QA audit of your product.