iamops.dev
Argo on X RSS feed
ENEnglish

Tools

HTTP client with OAuth, in your browser

Send a request with the auth method you need, including OAuth grants and an optional DPoP proof. The call goes from your browser to the API, not through this site.

Requests go from your browser to the API you enter, not through this site. Use test credentials only.

Requests leave your browser for the API you enter.

When you click Send or Get token, your browser calls that address directly. The request does not go through iamops.dev, and this site never sees the URL, the headers or the body.

Use test or sandbox credentials only. Never paste production secrets, passwords or live tokens.

Tokens and secrets stay in this tab's memory. If you opt in, the page can remember the configuration without the secrets.

Only test APIs you own or have permission to test.

This tool is provided as is, with no warranty.

Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.

How to get the input
  1. In DevTools > Network, right-click a request, choose Copy > Copy as cURL and paste it into the import box.Chrome DevTools: Network reference
  2. Save a HAR from DevTools > Network, as described on the HAR inspector page, and import one request from it.Chrome DevTools: save as HAR
  3. Most APIs publish an OpenAPI file, often at /openapi.json. Paste it, or a Postman collection export, and pick a request.OpenAPI Specification · Postman: export collections

Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.

What can I paste here#

The API URL and the credentials or token for the auth method you pick: Basic, Bearer, an API key, or OAuth settings such as issuer, client id, and for some grants a client secret or a refresh token. You can also paste a curl command, a HAR entry, or an OpenAPI or Postman definition to fill the form. Use test tenants and test secrets only.

HTTP client

Import

Paste a curl command, a HAR, an OpenAPI or Swagger document, or a Postman collection. Parsing stays in this browser. Secrets stay in memory and are not stored.

Stores method, URL, header names, endpoints and the client id on this device. Tokens, passwords and secrets are not stored.

Request as a command

Updates as you type. The Redact secrets in copies option applies here and to Copy.

Samples are made with throwaway keys and example.test names. They mean nothing outside this page.

How to read the result#

What it does not do#

Questions people ask#

What can I paste here

The API URL and the credentials or token for the auth method you pick: Basic, Bearer, an API key, or OAuth settings such as issuer, client id, and for some grants a client secret or a refresh token. You can also paste a curl command, a HAR entry, or an OpenAPI or Postman definition to fill the form. Use test tenants and test secrets only.

Does this HTTP client send my request through iamops.dev?

No. Your browser calls the API or the token endpoint directly. If that server does not allow cross-origin reads, the call fails in the browser and I offer the same request as curl.

Are my tokens saved?

No, not by default. Tokens and secrets stay in this tab's memory. If you tick Remember config without secrets, only non-secret settings such as the URL, client id and endpoints are stored on this device.

Which OAuth grants can I try?

Client credentials, authorization code with PKCE, device code, refresh token and RFC 8693 token exchange. You can also attach a DPoP proof built in the browser.

Related articles#

The newest posts and labs on the same topic, picked automatically.