Successful, Invalid, and Unauthorised Requests
Request testing distinguishes valid operations from malformed, impossible, unauthenticated, and insufficiently authorised attempts. Verify both the response and the resulting data state for every important request class.
What You Will Be Able to Decide
- Explain successful, invalid, and unauthorised requests in product and business terms.
- Apply this decision: Verify both the response and the resulting data state for every important request class.
- Recognise this material risk: the API returns an error while still making a partial or unauthorised change.
- Ask a consultant for evidence rather than reassurance.
A founder needs evidence that the product works beyond the most convenient demonstration path.
Request testing distinguishes valid operations from malformed, impossible, unauthenticated, and insufficiently authorised attempts.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
The Founder Situation
A founder needs evidence that the product works beyond the most convenient demonstration path.
The immediate question is successful, invalid, and unauthorised requests. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.
Technical term
Successful, Invalid, and Unauthorised Requests
Request testing distinguishes valid operations from malformed, impossible, unauthenticated, and insufficiently authorised attempts.
Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.
What Matters in Practice
Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.
For this decision, the useful standard is that the same expected result can be reproduced under normal, invalid, and failure conditions.
- Make the decision explicit: Verify both the response and the resulting data state for every important request class.
- Ask what evidence would show that the chosen approach works.
- Name the person or provider responsible when the approach fails.
- Record the result in the test plan and recorded evidence.
A Proportionate Decision
Verify both the response and the resulting data state for every important request class.
The principal risk is that the api returns an error while still making a partial or unauthorised change. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
Strong Evidence and Weak Reassurance
Warning Signs
- Nobody can explain how successful, invalid, and unauthorised requests changes a user or business outcome.
- The proposal does not address this risk: the API returns an error while still making a partial or unauthorised change.
- The only evidence is a successful demonstration of the easiest path.
- The decision has no named owner, boundary, or review point.
- A provider-specific feature is being mistaken for a permanent product requirement.
Questions to Ask a Consultant
- What decision are we making about successful, invalid, and unauthorised requests?
- Which user or business outcome does the recommendation protect?
- How have we reduced or accepted this risk: the API returns an error while still making a partial or unauthorised change.
- What evidence can I review without relying on the original implementer?
- What is deliberately deferred, and when will it be reconsidered?
- Who owns the accounts, data, documentation, and recovery process?
Key takeaway
Key Takeaway
Request testing distinguishes valid operations from malformed, impossible, unauthenticated, and insufficiently authorised attempts. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.