APITesterSources
Reference content is written from primary sources: the HTTP specifications (RFC 9110 for semantics, RFC 9111 for caching, RFC 5789 for PATCH), curl's own manual, and each provider's official documentation. Where common practice differs from a specification, the page says so. Pages that cite outside sources list them under a References heading, and those links go to the specification or the vendor, not to third-party summaries.
How examples are checked
- Curl examples. The commands on these pages are run before the page is published. Commands that depend on a local file, a private server or a tool that may not be installed cannot be checked the same way.
- Webhook examples. Payloads and headers follow each provider's documented format. They are representative, not captured from a live delivery: every id, token and signature is a placeholder, and the pages say so. Verification code is tested against the provider's published test values where the provider publishes them, and otherwise against signatures generated with the documented algorithm.
- Status codes and guides. Definitions follow the current RFCs rather than the superseded RFC 2616.
What can go out of date
Providers change header names, limits and retry schedules. Figures of that kind are described as correct at the time of writing, and each webhook page points to the provider's documentation as the source of truth. If a page and the official documentation disagree, trust the documentation and tell us.
Independence
api-tester.com is not affiliated with the API providers, services or tools it writes about. Pages that compare tools describe what each is suited to; the site's own tester is one of the options and its limits are stated on the about page.
Corrections
Mistakes are possible. Send the page address and what is wrong to support@api-tester.com; a link to the specification or documentation makes it quicker. Confirmed errors are corrected on the page itself.