Truthlocks provides public endpoints for resolving issuer identities using W3C Decentralized Identifiers (DIDs) and retrieving signing keys via JSON Web Key Sets (JWKS). These endpoints enable standards-based key verification without proprietary integrations.Documentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
DID resolution
Every issuer has a DID in the formatdid:truthlock:{issuer_id} that resolves to a W3C DID Document containing their public key material and service endpoints. DIDs are automatically assigned when an issuer is created.
Endpoint
Example request
Example response
Content-Type: application/did+json.
Verification method types
The key type in the DID Document depends on the issuer’s signing algorithm:| Algorithm | Verification type | JWK key type | Curve |
|---|---|---|---|
| Ed25519 | Ed25519VerificationKey2020 | OKP | Ed25519 |
| ES256 | JsonWebKey2020 | EC | P-256 |
| RS256 | JsonWebKey2020 | RSA | — |
JWKS endpoint
Retrieve all active public keys for an issuer as a standard JSON Web Key Set.Endpoint
Example request
Example response
When to use each endpoint
| Use case | Endpoint |
|---|---|
Verify a proof bundle offline using the issuer_did field | DID resolution |
| Validate JWT signatures from Truthlocks services | JWKS |
| Build integrations that follow W3C Verifiable Credentials standards | DID resolution |
| Integrate with existing OIDC/JWT infrastructure | JWKS |
Using DIDs in proof bundles
Theissuer_certificate.issuer_did field in a proof bundle contains the issuer’s DID. You can resolve it to retrieve the public key and independently verify the attestation signature without relying on Truthlocks infrastructure.
Related
- Proof bundle format — The cryptographic proof format that references issuer DIDs.
- Issuer keys API — Manage issuer signing keys.

