Secure & control
Bring your own JWT issuer
Trust any OIDC provider — register issuer/audience pairs with a JWKS URL and APIblaze verifies incoming JWTs and resolves the end-user id from the claim you choose.
- Any JWKS-backed OIDC issuer
- Multiple (iss, aud) pairs
- Pick the end-user id claim
- Trust is scoped per customer workspace (tenant)
curl — create trusting your JWT issuer
curl -sX POST https://api.apiblaze.com/proxy \
-H 'content-type: application/json' \
-d '{
"target": "https://api.example.com",
"requests_auth": {
"mode": "authenticate",
"methods": ["jwt"],
"jwt": { "allowed_pairs": [
{ "iss": "https://login.acme.com/", "aud": "acme-api",
"jwks_url": "https://login.acme.com/.well-known/jwks.json" }
] }
}
}'Federate without lock-in
Any issuer
Auth0, Okta, Cognito, your own — if it serves JWKS, it works.
Claim mapping
Resolve the end-user id from sub or any claim you name.
Tenant isolation
Issuer trust is scoped per tenant, so keys never cross.
Try it in 30 seconds
No signup required. Claim it to your account whenever you’re ready.