Get Application Credentials
Read one application’s full record including client_id and api_key. Use this to recover a lost api_key.
Documentation Index
Fetch the complete documentation index at: https://docs.didit.me/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
RS256-signed JWT access_token returned by POST /programmatic/login/ or POST /programmatic/verify-email/. Send as Authorization: Bearer <access_token>. Default lifetime is 86400 seconds (24h). This token is only valid against the Account Management endpoints on apx.didit.me/auth/v2. The verification API (verification.didit.me/v3) uses the long-lived api_key as x-api-key instead.
Path Parameters
UUID of the organization that owns the application.
"a1b2c3d4-5678-90ab-cdef-111111111111"
UUID of the application whose credentials you want to read.
"b2c3d4e5-6789-01bc-defg-222222222222"
Response
Application record including its client_id and api_key.
Full application record. uuid, client_id, and api_key never change after creation.
Application UUID. Use as {app_id} in subsequent calls.
"b2c3d4e5-6789-01bc-defg-222222222222"
Application display name shown in the Didit console.
"Acme Production App"
Public client identifier, safe to embed in OAuth-style flows.
"S9LIYGSoWNuGMLHsvEt9dQ"
Long-lived secret (also called client_secret). Use as the x-api-key header for every call to https://verification.didit.me/v3/... (sessions, workflows, AML, etc.). Treat as a credential; never expose client-side.
"05mHcOWL8GathLZlz8oIDawYj9qFAcoSHtz-75PAkuo"
Website or app URL associated with this application.
"https://acme.example"
Allowed redirect URIs for OAuth-style and verification redirect flows.
["https://acme.example/callback"]Terms of service URL shown in the verification flow.
"https://acme.example/terms"
Privacy policy URL shown in the verification flow.
"https://acme.example/privacy"
Internal description for the application (not shown to end users).
"2025-06-01T10:00:00Z"