client_id: Provided by your administrator, this identifies your application.
client_secret: A secret key provided by your administrator for authenticating your application.
audience: Specifies the target API, which should be "dcams.app".
grant_type: Always set to "client_credentials" for this type of request.
Responses
Create Session
After obtaining the Bearer token, you can create a verification session. This session will return a link that the user can use to complete the verification process.
Authorization: Bearer {{access_token}} (where {{access_token}} is the token obtained from the Authentication step)
Required Fields
email: The user's email address. This field is used as the primary identifier of a user, but the email address does not need to be real or working as we will never send the user an email.
age: The user's age, which must be in the format "21+" (with the plus sign to indicate "age to check and over"). NOTE: "21" is just the example, please use any value that fits your use case.
Optional Fields
When sending route_id, settings_id and/or brand_id as empty fielfds the default value for each that is associated with theclient_id will always be used.
route_id: The route ID to use for this session. If not provided, the default route associated with the client_id will be used.
settings_id: Specifies the settings for the session. If not provided, default settings associated with the client_id will be used.
brand_id: Specifies the brand for the session. If not provided, a default brand associated with the client_id will be used.
styles: Customize the appearance of the VX experience. See Styles for a full list of options.
webhook.endpoint: Provide the HTTPS endpoint that should receive VX webhook callbacks for this session. Make sure the endpoint is reachable from the public internet.
There are several more optional fields in the full example below.
Webhook deliveries can be protected with either Basic Authentication credentials or an HMAC signature header. Coordinate with your Veratad representative to receive the credentials or signing secret, and validate every webhook before processing it.
Request (Simple Example)
Request Body (Complete Example with All Optional Fields)
PRO TIP: Use the request_id to link the session back to your database through either a webhook or a poll request. Additionally, always use the returned link value, as the domain may change at any time.
You are limited to 1,000 requests per minute to the create session endpoint. If you require a larger throughput please contact our support team.
{
"message": "Bad JSON format",
"detail": "Please check your JSON and try again",
}
{
"message": "Unauthorized",
"detail": "Missing a required input"
}
{
"message": "Forbidden",
"detail": "Invalid API Key or missing token",
}
{
"message": "Already Verified", // this error only occurs if block setting is active
"detail": "This user has a status of pass"
}
{
"message": "Pending Review", // this only occurs if the VX app is a human review
"detail": "The user has a manual review of an ID document in process"
}
{
"message": "Too many requests",
detail: "You have exceeded the amount of requests",
}
{
"message": "Too many attempts", //this is enforced by email and visitor_id by default. In the case of creatng a session link at this time we will not have the visitor_id, and so, it will be based on email only.
"detail": "This user has exceeded the amount of verification sessions"
}
{
"message": "Internal Server Error",
"detail": "{{The reason for error if known}}"
}