Explorador de API
Prueba APIs REST en el navegador con respuestas JSON formateadas
Requests are sent directly from your browser using fetch(). The target API must allow CORS (Access-Control-Allow-Origin) for cross-origin requests to succeed. Public APIs like JSONPlaceholder work out of the box.
Test REST requests and inspect responses in one place
API debugging usually breaks across multiple tabs: one place for cURL, another for auth headers, another for JSON formatting. The API Explorer keeps the request, the response, and the formatted payload together, with browser mode for public APIs and proxy mode when CORS gets in the way. That makes it useful for classic REST APIs, AI inference endpoints, and JSON-based tool gateways.
Use the API Explorer when you need to
Replay a request from cURL
Paste a cURL command from docs, logs, or terminal history and import the method, URL, headers, auth, and body.
Inspect a JSON API response
Send the request, then switch between formatted, raw, and tree views without leaving the page.
Quickly debug auth, prompt, and header issues
Adjust bearer, basic, or API key auth alongside headers and resend the request in seconds, even when the body contains structured AI instructions or tool payloads.
How to test an API request quickly
- 1
Enter the request URL manually or import a cURL command from your terminal or API docs.
- 2
Choose browser mode for CORS-enabled APIs or proxy mode for blocked endpoints, then set the method, headers, auth, and request body.
- 3
Inspect status, timing, response headers, and the formatted JSON body to confirm what changed.
Keep going
Read the REST API testing guide
See a fuller workflow for reproducing and debugging API requests.
Format JSON payloads
Clean up copied request and response bodies before sharing or diffing them.
Compare two API responses
Spot structural changes between expected and actual payloads faster.
Inspect JWT tokens
Decode bearer tokens when an auth bug might be caused by claims or expiry.
Common API debugging workflows
Recreate the request in the browser, tweak one header, token, or JSON body field, and resend immediately.
Run the same request twice, then pass both payloads into JSON Compare for structural diffs.
Test auth, body shape, and response timing before you start debugging frontend code.
Herramientas relacionadas
LLM JSON Output Validator
Repair and validate model JSON output against a schema
Formateador JSON
Embellece y formatea JSON con sangría configurable
MCP Tool Schema Validator
Validate MCP tool definitions and verify `inputSchema` before deployment
Decodificador JWT
Decodifica tokens JWT: cabecera, payload y caducidad
Preguntas frecuentes
Introduce la URL de la API, elige el método HTTP (GET, POST, PUT, PATCH, DELETE), añade headers y un body si hace falta, y pulsa Send. La herramienta usa fetch() del navegador para hacer la petición directamente: no interviene ningún servidor backend.
Los errores CORS (Cross-Origin Resource Sharing) ocurren cuando el servidor de la API no incluye headers Access-Control-Allow-Origin en la respuesta. Es una medida de seguridad del navegador. APIs públicas como JSONPlaceholder suelen permitir CORS, pero muchas APIs privadas no. En ese caso, necesitarás un proxy CORS o probar desde un entorno server-side.
No. Las peticiones salen directamente desde tu navegador hacia la API objetivo usando fetch(). Nada pasa por nuestros servidores. Puedes comprobarlo en la pestaña Network del navegador: verás la solicitud yendo al endpoint de la API.
Sí. En la pestaña Auth puedes configurar Bearer token, autenticación Basic (usuario/contraseña) o un header personalizado para API key. Las credenciales se añaden automáticamente a los headers y se quedan solo en tu navegador.