Applications

curl -X GET 'https://identity.lucionglobal.com/api/developer/applications'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

curl -X POST 'https://identity.lucionglobal.com/api/developer/applications'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
  -H 'Content-Type: application/json'
  -H 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY'
  --data '{}'

curl -X PATCH 'https://identity.lucionglobal.com/api/developer/applications/{application_id}'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
  -H 'Content-Type: application/json'
  -H 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY'
  --data '{}'

curl -X DELETE 'https://identity.lucionglobal.com/api/developer/applications/{application_id}'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

curl -X POST 'https://identity.lucionglobal.com/api/developer/applications/{application_id}/rotate-secret'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
  -H 'Content-Type: application/json'
  -H 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY'
  --data '{}'

curl -X GET 'https://identity.lucionglobal.com/api/developer/applications/{application_id}/certification/status'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

curl -X POST 'https://identity.lucionglobal.com/api/v1/developer/applications'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
  -H 'Content-Type: application/json'
  -H 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY'
  --data '{}'

curl -X GET 'https://identity.lucionglobal.com/api/v1/developer/applications'
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

To register Lucion AI, open Identity Developer → Applications → Create application. Set the name to Lucion AI, choose Confidential, enter the exact redirect URI https://chat.lucionglobal.com/auth/callback, keep openid, profile, and email selected, and leave optional API permissions unchecked unless the integration needs them. Submit after signing in and completing the step-up check. The confirmation shows the public Client ID and the distinct client secret in separately labeled fields.

The Client ID is normal application metadata and stays visible in this page. The confidential client secret is generated independently with cryptographic randomness; Lucion stores only a one-way hash verifier and never stores the plaintext. The confirmation is the only time that secret can be read. Save it in a server-side secret manager. The card shows whether an active verifier is configured and when it was last rotated, never the secret itself.

To change a name, description, homepage, exact redirect URI list, or allowed scopes, choose Edit settings. The Client ID and client type do not change. For a lost or exposed secret, choose Rotate secret, confirm step-up, and update the integration immediately: the old secret is revoked as the replacement is issued, and the new value is shown once. Delete application disables it and revokes its keys, OAuth grants/tokens, consents, webhooks, and delegations. Lucion retains a non-secret audit tombstone; user accounts are not deleted.