Skip to content
← All tools

APIs & HTTP tools

Turn raw HTTP traffic into something you can read and reuse.

These tools convert between cURL commands and code snippets, summarize HAR captures, parse header blocks, and check webhook signatures. They are built for debugging integrations: paste what you captured, review the parsed result, and keep credentials out of the output.

Nothing is requested or evaluated. URLs are never contacted, JavaScript is never executed, and redaction is applied before anything is displayed.

Which tool for which job

Reproducing a request is the most common API debugging task. If you have a cURL command from documentation or from your browser's "Copy as cURL", convert it to fetch for JavaScript or to Python requests for a script. If you have front-end code and need to hand a reproducible request to a backend team, convert fetch to cURL. The HTTP header parser and response inspector break pasted traffic into readable parts, and the HAR viewer summarizes a whole browser session recorded in DevTools.

For integrations, the webhook signature verifier checks whether an HMAC signature matches a payload and secret, which is the first thing to rule out when a webhook endpoint rejects events. The OpenAPI validator catches structural mistakes in a JSON specification before you feed it to a code generator or documentation tool.

Sharing debugging output safely

API traffic is full of credentials: bearer tokens, API keys, cookies, and signing secrets. Every tool here redacts sensitive headers by default, and none of them sends a request. That makes the output safe to paste into an issue tracker or a chat with a vendor's support team. Turn redaction off only for a local copy you need to run yourself.

When you report an API problem, include the method, URL, relevant headers, request body, status code, and response body, with secrets removed. A cURL command plus the response usually lets the other side reproduce the issue in minutes instead of days.