Update application metadata for an application in your organization. This is useful for resellers that maintain one application per customer, or for organizations that separate products, brands, regions, environments, or verification use cases.
Use this endpoint to keep each application aligned with the customer, brand, environment, or internal use case it represents. For resellers, this lets you rename or update each customer application without sharing credentials across customers. For direct customers, it helps separate products, regions, or environments while keeping everything under one organization.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.
api_key stays the same unless you rotate credentials separately.Access token from login or verify-email response
Application display name.
Website or app URL associated with this application.
Allowed redirect URIs for OAuth-style flows.
Terms of service URL shown for this application.
Privacy policy URL shown for this application.
Internal description for the application.
Application updated. Existing api_key remains valid.
Your API key. Use as the x-api-key header for Didit verification API calls on https://verification.didit.me/v3. This is the same value as client_secret.