# Test HTTP and OAuth APIs in your browser

> Call an API from your browser with Basic, Bearer, an API key or OAuth 2.0, including PKCE. Optional DPoP. The request never goes through this site.

- URL: https://iamops.dev/tools/http-client/
- Markdown: https://iamops.dev/tools/http-client.md
- Language: en
- Runs in your browser, nothing is uploaded.

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.

## 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.

## What it does

- Set method, URL, headers, query and body, then send the request from your browser.
- OAuth 2.0 grants include client credentials, authorization code with PKCE, device code, refresh and RFC 8693 token exchange. OIDC discovery can fill the endpoints.
- If the server blocks browser calls, you get a clear CORS message and a curl command. Secrets stay in this tab unless you opt in to remember the configuration without them.

## Example use

Point the client at a test token endpoint, choose client credentials or authorization code with PKCE, and read the token or the CORS error with the matching curl command.

## How to read the result

- Send calls the address from your browser. This site never proxies the request. If the server does not allow CORS, you get a clear message and a curl command instead.
- For OAuth, fill the issuer and use Fill from issuer when the discovery document is readable. Get token runs the grant you picked and, if it works, applies the access token to the request.
- Authorization code with PKCE opens a pop-up when the browser allows it, then returns here and checks state. The verifier stays in this tab until the exchange is done.
- DPoP builds an ES256 proof in Web Crypto and sends it on the token call and on the API request. The key lives in memory only.

## What it does not do

- Many token endpoints refuse cross-origin calls from a browser. I cannot work around that without a server proxy, which this page will not do.
- I do not store tokens unless you opt in to remember the configuration, and even then secrets are left out.
- This is a tester, not a full API client. There are no collections, environments or cookie jars.

## 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.

## Open a mode directly

You can open this tool with a mode already selected by adding a #mode= fragment to the address. Never put secrets in the URL. The fragment only names a mode.

- [Basic](https://iamops.dev/tools/http-client/#mode=basic): `#mode=basic`
- [Bearer](https://iamops.dev/tools/http-client/#mode=bearer): `#mode=bearer`
- [API key](https://iamops.dev/tools/http-client/#mode=apikey): `#mode=apikey`
- [OAuth 2.0 client credentials](https://iamops.dev/tools/http-client/#mode=cc): `#mode=cc`
- [OAuth 2.0 authorization code and PKCE](https://iamops.dev/tools/http-client/#mode=code): `#mode=code`
- [OAuth 2.0 device code](https://iamops.dev/tools/http-client/#mode=device): `#mode=device`
- [OAuth 2.0 refresh token](https://iamops.dev/tools/http-client/#mode=refresh): `#mode=refresh`
- [RFC 8693 token exchange](https://iamops.dev/tools/http-client/#mode=exchange): `#mode=exchange`

## Related

- [Certificate decoder](https://iamops.dev/tools/certificate-decoder.md): Decode an X.509 certificate, chain or CSR and read SANs, expiry, key size, fingerprints and chain order. Paste PEM, base64 DER or hex. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/certificate-decoder/)
- [SAML decoder and verifier](https://iamops.dev/tools/saml.md): Decode a SAMLRequest or SAMLResponse, check the XML signature and decrypt an EncryptedAssertion. Paste base64, raw XML or a redirect URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/saml/)
- [JWT decoder and verifier](https://iamops.dev/tools/jwt.md): Decode a JSON Web Token, show claims and expiry as dates, and verify the signature. Paste a compact JWT, then an HMAC secret, PEM key, JWK or JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/jwt/)
- [ID-JAG inspector](https://iamops.dev/tools/id-jag.md): Inspect an Identity Assertion JWT Authorization Grant against the IETF draft and get the curl requests. Paste a compact ID-JAG token. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/id-jag/)
- [DPoP proof builder and checker](https://iamops.dev/tools/dpop.md): Build a DPoP proof with a fresh ES256 key, or check typ, htm, htu, iat, ath, nonce and the cnf.jkt thumbprint. Paste a DPoP JWT and the method and URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/dpop/)
- [PKCE generator](https://iamops.dev/tools/pkce.md): Generate a PKCE code verifier and S256 challenge, or check that a pair matches, with authorize and token snippets. Paste a verifier and optional challenge, or generate them here. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/pkce/)
- [OIDC discovery and JWKS viewer](https://iamops.dev/tools/oidc-discovery.md): Read an OpenID Provider discovery document and JWKS, and flag missing PKCE, weak keys or risky grants. Type the issuer, or paste the JSON if CORS blocks the fetch. Runs in your browser. Nothing is uploaded to this site; the fetch goes from your browser to the issuer. (https://iamops.dev/tools/oidc-discovery/)
- [Encoder and decoder](https://iamops.dev/tools/encoder-decoder.md): Encode or decode Base64, URL, hex, HTML entities, Unicode, gzip, deflate and the SAML redirect chain, with auto-detect. Paste the text. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/encoder-decoder/)
- [HAR inspector](https://iamops.dev/tools/har-inspector.md): Inspect a HAR file: filter requests, follow the OAuth or SAML flow, decode JWTs, and copy as curl with secrets redacted. Drop a HAR export from DevTools. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/har-inspector/)
- [SD-JWT and VC decoder](https://iamops.dev/tools/sd-jwt.md): Decode an SD-JWT or SD-JWT VC: split disclosures, recompute digests against _sd, and check the Key Binding JWT. Paste the compact string with ~ separators, and optionally the issuer JWK. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/sd-jwt/)
- [Passkey and WebAuthn decoder](https://iamops.dev/tools/webauthn.md): Decode a WebAuthn or passkey response: attestationObject, clientDataJSON and authenticator data, including flags, AAGUID, sign count and the COSE public key. Paste the credential JSON or the individual fields. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/webauthn/)
- [MCP auth discovery checker](https://iamops.dev/tools/mcp-auth.md): Check MCP authorization discovery: Protected Resource Metadata (RFC 9728) and the authorization server metadata, and flag missing PKCE S256, CIMD/DCR or resource indicators. Enter the server URL, or paste the JSON if CORS blocks the fetch. Requests go from your browser, nothing is uploaded to this site. (https://iamops.dev/tools/mcp-auth/)
- [Shared Signals SET decoder](https://iamops.dev/tools/shared-signals.md): Decode a Shared Signals Security Event Token (CAEP or RISC), explain the event type and the sub_id formats, and optionally verify the signature. Paste the SET JWT and optionally the transmitter JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/shared-signals/)
