Authorization

The Authorize Endpoint is used to obtain a server token that allows a client’s server to create a verification request or fetch verification results securely. Since identity verification data is sensitive, authentication is required to ensure that only authorized servers can access it.

To generate a server token, Incode will provide the following credentials:

The server token is valid for 15 minutes, after which a new authorization request must be made. This ensures security while maintaining seamless integration for verification workflows.

Endpoint

POST/v1/integration/authorize/server

Headers

Header Description Required Example Value
x-api-key API key is provided by Incode Yes abcdefg12345678
Content-Type Supported content type for this request is application/json Yes application/json

Request Parameters

Parameter Description Required Example Value
integration_id The integration ID, representing the unique identifier for the client integration. This value can be found on the Integration card for custom integration. Yes c0fd10ff-c36e-49a6-afde-a00496c1c8e7
secret A secret parameter for additional security. This value can be found when custom integration is opened. Yes s3cureS3cr3tValue

cURL Example

Demo server URL: https://demo-api-incode-id.incodesmile.com

Production server URL: https://api-incode-id.incodesmile.com

curl --location 'https://{server-url}/v1/integration/authorize/server' \
--header 'x-api-key: 4115e33314e12c0effe540c74bac55937b65a448' \
--header 'Content-Type: application/json' \
--data '{\n    "integrationId": "621cda6e-c7de-4ebd-9219-a137a84a5211",\n    "secret": "s3cureS3cr3tValue"\n}'

Response

Status Code:200 OK

Success Response

JSON

{
    "token": "eyJhbGciOiJIUzI1NiJ9..."
}

The response contains a token, which is required for requesting verification and fetching verification data.

Token Validity