California DMV Digital Signature Verification API v1
This section describes how to integrate with the California DMV Digital Signature Verification v1 API. For developers already familiar with our platform, the v4 API is also available and uses a standardized response model — see DMV Digital Signature Verification API v4.
Endpoint URL
https://screening.idscan.net/api/Check
HTTP Method
POST
Content Type
application/json
Authorization
This API uses Bearer Token authentication. Include the following header in your request:
Authorization: Bearer {YOUR_TOKEN_HERE}
Important
Be sure there is a one space between Bearer and {YOUR_TOKEN_HERE}
If you are already familiar with our platform, you can obtain your API token by visiting the Screening Service Web portal. Detailed instructions on finding your token are available in our documentation.
If you are new to our platform, please contact our team at sales@idscan.net to get started, or reach out to support@idscan.net with any questions.
Request Data
{
"services": [
"19862c3a-513f-4d48-ab36-fa583e8df90a"
],
"trackString": "@\n\nANSI 636014100102DL00410294ZC03350220DLDAQD12345671\n..."
}
Request fields description
| Field Name | Required | Type | Possible Values |
|---|---|---|---|
| "services" | Yes | Array[string] | Must contain exactly: "19862c3a-513f-4d48-ab36-fa583e8df90a" |
| "trackString" | Yes | String | Raw PDF417 barcode string read from the back of the document |
Important
When the "services" field is null or is an empty array, all services enabled on your account will run. We do not recommend submitting requests this way. Be explicit about which services you want to run.
Response Data
[
{
"serviceId": "19862c3a-513f-4d48-ab36-fa583e8df90a",
"serviceName": "DMV Digital Signature Verification",
"serviceDescription": "Verifying Digital Signatures on US DL/ID Documents",
"error": null,
"success": true,
"locationId": null,
"readOnlyAccessLocationIds": null,
"metadata": {},
"profiles": [
{
"firstName": "JOHN",
"middleName": "NONE",
"lastName": "SAMPLE",
"fullName": "JOHN NONE SAMPLE",
"dateOfBirths": "01/11/1990 12:00:00 AM",
"sex": "Male",
"address": "1234 MAIN STREET APT 101",
"city": "SAN FRANCISCO",
"state": "CA",
"zipCode": "94102-0000",
"idNumber": "D12345671",
"issuedBy": "CA",
"dmvDigitalSignatureVerificationResult": {
"isValid": true,
"isRevoked": false
}
}
]
}
]
Response fields description
A successful verification returns an array with one element per service. The key result object is dmvDigitalSignatureVerificationResult inside profiles[0]:
| Field | Type | Description |
|---|---|---|
isValid |
bool / null | true if the cryptographic signature is valid;false if invalid;null if the check could not be performed. |
isRevoked |
bool / null | true if the document has been revoked by the DMV;false if it is still active;null if the check could not be performed. |
success(bool):trueif the request completed without errors. Iffalse, check theerrorfield for the message.error(string | null): Error message string whensuccessisfalse; otherwisenull.
CURL request
curl -X POST https://screening.idscan.net/api/Check \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR-TOKEN-HERE" \
-d "{\"services\":[\"19862c3a-513f-4d48-ab36-fa583e8df90a\"],\"trackString\":\"@\\n\\nANSI 636014100102DL...\"}"
Test cases
You can test and receive all verification statuses with your TEST token. Test cases are available here.
Error handling
Common errors are described here. Additional errors specific to this service are described here.