Create a new application inside one of your organizations. Use this for reseller models where each customer gets a separate application, or to separate products, brands, regions, environments, or use cases inside the same organization. The response includes a client_id and api_key for the new application.
Use this endpoint when you need to separate verification traffic, credentials, branding, or reporting inside the same organization. This is especially useful for resellers that create one application per customer. It also works well when your own company has multiple products, brands, regions, staging/production environments, or use cases that should not share the same API key and application-level settings.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.
https://apx.didit.me/auth/v2. Use the returned api_key as x-api-key when calling https://verification.didit.me/v3/... endpoints such as sessions and workflows.Access token from login or verify-email response
Application display name. Defaults to the organization name plus App.
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 created. Store the api_key securely and use it as x-api-key for verification.didit.me /v3 calls.
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.