Reverify a Verification
DeprecatedReverifies a Verification request, provided the request is already in a completed state and no more than 90 days have passed since completion of the verification
Path parameters
Verification ID
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.
Specify the content type and version that the API should use. It’s recommended to include this to avoid breaking changes.
A header that defines if a request should be executed synchronously. Only Verifications that were initially executed synchronously may be reverified synchronously. sync
can only return completed or canceled verification responses, not pending. async
will return only pending.
Request
Response
Reverification Request Created.
A valid purpose is required for Truework to process the verification request.
Throughout the API, this is signified by the permissible_purpose
field.
Currently we only support USD as currency. Currency amounts are represented as strings with two decimal precision, e.g. “34.95”.
The state helps convey where the verification request is in the Truework process. It will be returned in the JSON objects returned from this endpoint.
The initial state of all Schemas is pending-approval, and will switch to processing once Truework begins to process the request. However, it may switch back to pending-approval if it is pending approval by the target.
The states completed, canceled, invalid are all terminal states of a Verification. A Report is only available when it is in the completed state. A Verification will enter the state canceled when either Truework or an API user cancels the request. The invalid state indicates that there are issues with the data e.g. we could not locate the employee at a given employer, or could not find the employer itself.
We use data from thousands of verification requests to estimate the duration between creation and completion of a request. For a provided company, upper_bound and lower_bound are the time estimates (in hours) that this particular request will take to be fully processed by Truework. May be an empty if an estimate does not exist for the verification request.
The verification request use case describes the type of product the verification request is originating from. If omitted, the verifier type in account settings will be used as a default
Any additional information about the target that can help expedite the completion of the verification request
The details for the cancellation; only present when state is canceled
The date when this verification was completed in ISO 8601 format
Supporting documentation files provided by the verifier for the verification
The loan id associated with the verification request
A single level key-value JSON object that can be used to store custom data on the verification request; keys and values must be strings
Applicable reports belonging to this request, if the request has been completed
The originating party that requested the verification via a reseller.