Create New Document.
Authentication
Headers
Request
When an ID document is created/uploaded, it is assigned a documentId. You’ll see this in a successful response or successfully accepted response. This can then be referenced in subsequent calls if you’re uploading more/updated data.
Set of key-value pairs that provide ID type-specific data. If updating an existing document, then existing values with the same name will be overwritten. New values will be added.
If this document is scanned through OCR or similar processes, then extracted data will be found here (Some may be used to populate other fields like idNumber and idExpiry as well)
The expiry date of the document (if known) in YYYY-MM-DD format.
The issued date of the document (if known) in YYYY-MM-DD format.
The ID number of the document (if known).
The sub-type of identity document. Very document specific.
Response
The request was valid and able to be processed in some fashion. Results may or may not be successful, but it was completed as far as practical with no actual errors. Returns the document object as it stands now. No docScan file data will be returned unless the /full variant is requested.
Unique identifier for every request. Can be used for tracking down answers with technical support.
Uses the ULID format (a time-based, sortable UUID)
Note: this will be different for every request.