This authentication function is the recommended alternative of using a secret key for API integrations.
It uses:
username- account emaildeveloper_key- API Key (public identifier)secret_key- Secret Key (confidential)
⚠️ Secret Key is confidential and must not be shared
An authorization token is returned (valid for 1 hour) and must be included in all subsequent API calls.
Secret Key can be generated and managed from the account's Developer page.
The legacy password-based method (GET https://api.liveconsent.com/LCSWS/account/authentication) remains available but will be deprecated in the future.
We recommend all new integrations use this method instead.
API function usage type: Standard| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Token lifecycle
Each authorization token is valid for 1 hour from the time it is generated.
To limit unnecessary token generation, the authentication endpoint reuses an existing token when possible:
- More than 5 minutes of validity remaining: the existing token is returned with its original
expires_at. - No active token, or 5 minutes or less of validity remaining: a new token is generated with a new 1-hour validity period.
Integrations should store both authorization_token and expires_at, and reuse the current token until it approaches expiration.
Recommended renewal strategy
Request authentication again approximately 4 minutes before
expires_at. This ensures the request falls within the renewal window while avoiding unnecessary authentication calls.
Early authentication calls
Calling the authentication endpoint before the renewal window does not extend the validity of the current token. The existing token and its original
expires_atare returned.