Skip to main content
POST
/
title
/
{id}
/
data
cURL
curl --request POST \
  --url https://api.cardinalzyn.com/title/{id}/data \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "sync_nmvtis": false,
  "sync_public": false,
  "sync_private": false,
  "dppa_exemption": "legitimate_business_need"
}
'
{
  "entryId": "<string>",
  "job_status": "enriching"
}
Requests a DMV, public, or NMVTIS enrichment job for an existing title entry. At least one sync flag must be true: sync_nmvtis, sync_public, or sync_private. The API returns 400 both when no sync type is requested and when the title entry is not found. It returns 409 when the entry exists but is missing account_data, which is required for enrichment.

Authorizations

​
Authorization
string
header
required

API key or Clerk JWT supplied as Authorization: Bearer

Path Parameters

​
id
string
required

Unique identifier of the title entry

Body

application/json

Data sources to fetch from. At least one sync flag must be true.

​
sync_nmvtis
boolean
default:false

Fetch data from NMVTIS (National Motor Vehicle Title Information System)

​
sync_public
boolean
default:false

Fetch data from public DMV websites.

​
sync_private
boolean
default:false

Fetch vehicle title and registrant information from private DMV portals.

​
dppa_exemption
string
default:legitimate_business_need

Driver's Privacy Protection Act exemption code passed through to private/NMVTIS enrichment requests when provided

Response

Data enrichment or processing initiated successfully

​
entryId
string
required

ID of the title entry being processed

​
job_status
enum<string>
required

Will be 'enriching' if successful, 'error' if failed

Available options:
pending,
input_parsing,
enriching,
generating_forms,
complete,
error
Example:

"enriching"