VoriTools

Explore API definitions and generate request code

Paste the definition, select an endpoint and enter sample parameters. Review the generated code before running it in your own API client.

Runs locally in your browser
View category: API Development (15)
API definition

Paste an OpenAPI 3.x or Swagger 2.0 document in JSON or YAML. Nothing is uploaded or fetched by this tool.

Available operations
Analyze a definition to browse its endpoints.
Request builder

Choose an endpoint above to create its path, query, header, and body fields.

Select an endpoint to generate a cURL command.
Select an endpoint to generate Fetch code.

Explore an API specification without sending it anywhere

OpenAPI Explorer reads local JSON or YAML, surfaces endpoints and required inputs, and creates request snippets you can adjust before using in your own API client. It deliberately does not send requests, tokens, or specifications to another service.

How to build a request from a definition

Paste an OpenAPI 3.x or Swagger 2.0 definition to list every operation it declares, fill in the parameters it documents, and copy a cURL or Fetch snippet for the endpoint you choose.

The definition, the server URL and the bearer token stay in the browser. The document is parsed locally and no request is sent to your API from this page.

  1. Paste the definition into the editor as JSON or YAML, or press Load example to start from a sample.
  2. Press Analyze definition. The operation list shows each method and path; if the document has no version marker, or no operations under paths, the status line says so instead.
  3. Choose an operation to build its parameter form from the definition: path, query and header fields, plus a request body when the definition describes one.
  4. Fill the required fields. Every documented parameter has to be present before code can be generated, and the status line names the first one still missing.
  5. Press Generate request code, then Copy cURL or Copy Fetch. Set the server URL or a bearer token first if the endpoint needs them.

What the builder does and does not do

Which definitions are accepted

OpenAPI 3.x and Swagger 2.0 are both read, in JSON or YAML, and the version marker decides how servers, parameters and request bodies are interpreted. A document with neither marker is rejected with a message naming the root field that is missing.

Operation rows are built from the paths object: one row per method, labelled with the path and the operation summary, or "No summary provided" when the definition omits it.

Generated snippets are a starting point

VoriTools writes the request from the definition and never executes it. Nothing is sent to your API from this page, so a token you type is used only to fill in the snippet text.

The snippet carries the parameters and headers the definition documents. Anything it does not describe — retries, signing, pagination, OAuth flows — has to be added in your own client.

Frequently asked questions

Does this tool call my API?

No. It reads the definition and writes request code; the request itself is never executed here, so no traffic reaches your API from this page.

Which definition formats are supported?

OpenAPI 3.x and Swagger 2.0, written as JSON or YAML. The version marker at the document root determines how each field is interpreted.

Recent tools: