Create Title Entry
Create a new title entry with vehicle information or document uploads
account_data, document URLs, or a raw array of document URLs. If an entry with the same VIN already exists for your organization, Porter updates the existing entry instead of creating a duplicate.
Response Variants
This endpoint returns HTTP200 for successful creates and updates.
pending for new entries, or enriching when an existing VIN is updated and a sync flag was requested.{entryId, job_status} response.
Notes
- A raw JSON array is accepted as a legacy shorthand for
{ "attachments": [...] }. - If
sync_publicorsync_privateis requested without an issuing state, the API automatically enablessync_nmvtis. dppa_exemptionis optional on create. When provided, it is passed through to enrichment requests.
Authorizations
API key or Clerk JWT supplied as Authorization: Bearer
Body
Title entry data - either structured AccountData or document URLs for processing
Recommended format: combine document uploads with partial structured data for best results
Array of document URLs to be processed via OCR and data extraction. Supported formats: PDF, JPG, PNG
Additional structured data, such as loan applicant information. Data will be intelligently merged with OCR-extracted data.
Optional user group ID for organizational access control and workflow routing
Whether to sync NMVTIS data
Whether to sync public DMV data
Whether to sync private DMV data
Driver's Privacy Protection Act exemption code. Passed through to enrichment requests when provided; create requests do not validate it as required.
Accepted for legacy clients but ignored; the organization is derived from authentication.
Response
Title entry created or existing entry updated. The response variant depends on VIN deduplication and requested sync flags.
New entry created; job_status is pending