Practical guide · November 16, 2026
What should you prepare before an API penetration test?
Prepare an accurate API inventory, representative accounts, test data and written rules for what the testers may do. The goal is to let the team examine the intended workflows and permission boundaries without spending the engagement discovering missing access or accidentally triggering real business actions.
OWASP's API inventory guidance calls attention to hosts, environments, versions, documentation and third-party data flows. Those are useful inputs to a testing brief, though its API Top 10 is not a complete engagement plan. OWASP API inventory guidance
Give the tester a map of the service
Hypothetical preparation record: A SaaS company exposes a customer API and an older partner API.
| Item | Example entry | Question to settle |
|---|---|---|
| Customer API | Current version in staging | Which production differences remain? |
| Partner API | Older version still used by one partner | Is it included or explicitly excluded? |
| Tenant accounts | Two synthetic customer organizations | Which data should each account access? |
| Privileged role | Restricted support account | Which support actions are intended? |
| Integration | Billing provider sandbox | Can any call trigger a real charge or message? |
Replace descriptive labels with the actual authorized hosts and identifiers in the private engagement brief. Keep credentials in an approved delivery channel, not in a broadly shared planning document.
Describe expected permissions
For each role, state which objects and operations it should access. “Admin and user accounts supplied” leaves important questions open: admin of which tenant, allowed to do what, and under which conditions?
Include representative workflows such as creating, reading, changing and deleting a test record. Ask the tester which additional roles or relationships are needed to evaluate the agreed scope. Do not assume one powerful account can stand in for every lower-privilege user.
A filled permission matrix
Fictional expected behavior, agreed with the product owner before testing. Tenant A and Tenant B contain synthetic invoices only.
| Role | Tenant/object | Operation | Expected result |
|---|---|---|---|
| A billing admin | A invoice A-101 | Read and amend draft | Allowed |
| A read-only member | A invoice A-101 | Read / amend | Read allowed; amendment denied |
| A billing admin | B invoice B-201 | Read or amend | Denied |
| B billing admin | B invoice B-201 | Read and amend draft | Allowed |
| Support, no active customer grant | A or B invoice | Read contents | Denied |
| Support, active scoped grant for A | A invoice A-101 / B invoice B-201 | Read | A allowed; B denied; grant expiry retained |
Readiness check: On November 16 the owner authenticates each synthetic role against staging build api-42 and confirms fixture creation and reset. The B admin account initially fails to authenticate, so cross-tenant coverage is marked blocked until its access is repaired and checked. That walkthrough verifies preparation; it is not a penetration-test result. Deliver the matrix with the scope and environment plan, and carry any unresolved limitation into the report.
Make documentation executable in practice
Supply current schemas or request collections where available, authentication instructions, setup steps and a way to create or reset test data. Have the internal owner demonstrate a representative workflow before the engagement starts.
If the documented endpoint no longer works, resolve the mismatch or record it. If an old version remains reachable, make an explicit scope decision. OWASP identifies outdated documentation and unmanaged API versions as inventory risks; silently omitting them from the briefing hides a relevant uncertainty. OWASP API9
Agree operational boundaries
Record permitted environments, test windows, sensitive operations, traffic limits, emergency contacts and stop conditions with the testing team. Identify dependencies you do not own and establish the necessary authorization before including them.
In the example, a test refund must not reach a live payment service. The owner checks configuration and test credentials rather than relying on the word “staging.”
Finish with a readiness walkthrough: the tester can authenticate, use the supplied roles, create synthetic records and reach the agreed scope. Log unresolved exclusions so the final report can explain what was not assessed.
Evidence reviewed November 16, 2026. OWASP provides inventory principles; the preparation worksheet is an original fictional example, not a completed penetration test.