JWT Decoder & Verifier β Bulk
Pricing
from $0.0005 / jwt processed
JWT Decoder & Verifier β Bulk
Decode JWT header and payload, and optionally verify the signature and expiry against a secret or JWKS. Debug and audit auth tokens in bulk.
Pricing
from $0.0005 / jwt processed
Rating
0.0
(0)
Developer
hiper soft
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
Decode JWT header and payload, and optionally verify the signature and expiry β in bulk. Debug auth tokens, inspect claims, and audit expiry across many tokens at once, with support for HMAC secrets and JWKS-based verification.
What it does
- Decodes the header and payload of each JWT (claims, issuer, subject, audience, timestamps).
- Flags expired tokens.
- Optionally verifies the signature against a secret / public key, or a JWKS endpoint (RS256/ES256).
Use cases
- Backend debugging β inspect what a token actually contains.
- Auth audits β check claims and expiry across many tokens.
- Integration testing β verify tokens from an identity provider.
Input
{ "tokens": ["eyJhbGci..."], "secret": "", "jwksUri": "" }
| Field | Type | Description |
|---|---|---|
tokens | array | JWTs to decode/verify. |
secret | string | Optional HMAC secret or PEM public key. |
jwksUri | string | Optional JWKS endpoint for RS/ES tokens. |
Output
{ "algorithm": "HS256", "issuer": "acme", "expiresAt": "2026-01-01T00:00:00.000Z", "expired": true, "signatureVerified": null, "valid": false, "payload": { "sub": "1234567890" } }
Output schema
| Field | Type | Description |
|---|---|---|
valid | boolean | Signature verified AND not expired. |
expired | boolean | Whether the token is past its exp. |
algorithm | string | Signing algorithm. |
FAQ
Can I verify signatures? Yes β provide a secret/public key, or a jwksUri for provider-signed tokens.
Can I automate it? Yes β via integrations on the Apify platform and the Apify API.
Notes
Original clean-room implementation. Tokens are processed only to decode/verify them.