Postman API Documentation Completeness and Accuracy Audit
Check docs against actual behaviour.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit API documentation. Documentation text per endpoint: [DOCUMENTATION]. Actual responses observed in tests (invented or anonymised): [OBSERVED_RESPONSES]. Report endpoint by endpoint with a status of accurate, minor mismatch or wrong, quoting the documentation line and the observed value side by side. Compare fields, types, status codes and error messages. Count each status and show the percentage of accurate endpoints, with arithmetic. Distinguish documentation that is wrong from behaviour that is probably a bug (put the latter on a separate list for the API owner), and separate confirmed mismatches from suspicions. Check that examples are complete and consistent, every error response has an example, authentication steps work in order, rate limits and errors are explained, and the version is stated. Return a table and a fix list, with facts needing the API owner marked [VERIFY], and a process rule: documentation updates are part of the definition of done for API changes.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.