How do I send an API request online?
Pick a method, type the URL and press Send, or Ctrl+Enter. Query parameters, headers, a JSON, form, multipart or file body, and auth each have a tab under the URL; a query string pasted into the URL moves into the parameters table on its own. The response shows its status, time and size, with the body formatted as JSON, as raw text, or previewed as an image or an HTML page. Variables written as {{name}} are filled in from the collection or the active environment, and the line under the URL shows exactly what will be sent before you send it.
Why does my request fail here when it works in Postman or curl?
Almost always CORS. Postman and curl are programs on your computer, but this client is a web page, and a browser only lets a page read a response from another site when that site allows it with an Access-Control-Allow-Origin header. Public APIs often do; internal and third-party APIs often do not. When the browser blocks a request it tells the page nothing more than that it failed, so the message lists the likely causes and the browser console (F12) has the exact one. If the API is yours, allowing https://oktools.dev in its CORS settings makes it work. A browser also will not let a page set Cookie, Host, Origin or Referer headers, or call a plain http:// address other than localhost from an https page.
Can I import an OpenAPI or Swagger spec and try its endpoints?
Yes. Paste the spec, open the file or fetch it by URL under Import / export, and every operation becomes a request, in a folder per tag. The first server becomes a {{baseUrl}} variable, path and query parameters are filled with the spec's examples, a JSON body is written from the request schema, and auth is set up from the security schemes, with {{token}} or {{apiKey}} variables to fill in once. Each response is then checked against the spec: whether its status code is documented, and whether a JSON body matches the documented schema, with every mismatch named by its path.
Can I import a Postman collection or a curl command?
Both. A Postman v2.1 collection keeps its folders, requests, variables and auth, and a Postman environment becomes an environment you can switch to; pre-request and test scripts are not run. A curl command — such as one copied from the browser's network tab with "Copy as cURL (bash)" — becomes a request with its method, headers, body and Basic or Bearer auth. The Code tab goes the other way, writing any request as a curl command or a JavaScript fetch() call.
Is anything I enter saved or sent to oktools.dev?
No. The collection, environments, tokens and history live only in this tab's memory: nothing is written to localStorage, IndexedDB or a cookie, and a reload starts over from the sample. To keep your requests, export them as a Postman file, with secrets left out unless you tick the box. Requests travel straight from your browser to the API you name and never pass through oktools.dev. Because this page, like any web page, also runs a third-party analytics script, use test or short-lived credentials here rather than production secrets.
Which authentication methods does it support?
Bearer tokens, Basic auth, API keys in a header or the query string, and OAuth 2.0 with the authorization code flow (always with PKCE), client credentials or a username and password. For the authorization code flow, register https://oktools.dev/oauth-callback.html as a redirect URL with your provider: sign-in happens in a popup, and the token is held in this tab only. Auth can be set once on the collection and inherited by every request, or overridden on any one of them.
Can it call an API running on localhost?
Yes, as long as the local server answers CORS requests from https://oktools.dev. Browsers allow an https page to call http://localhost, but not other plain http:// addresses, and Chrome asks once for permission before a public site may reach your own machine or local network. Requests use your browser's own network connection, so a VPN or corporate network your browser is on is reachable too.