Update identity verification in batch | Cable

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

An array of identity verification update payloads. Each payload must include the ‘verification_id’ to identify the identity verification and can include any other fields that need to be updated. The ‘timestamp’ field represents the time of update.

verification_idstringRequired

This can reference:

Your internal verification record ID
The original provider’s verification ID (optionally with a prefix)
Any unique identifier that allows traceability to the original data source

Unique identifier for an identity verification. This is the primary identifier for an identity verification and should be unique across all identity verifications. Updates to an identity verification should be made using this identifier. This can reference: - Your internal verification record ID - The original provider's verification ID (optionally with a prefix) - Any unique identifier that allows traceability to the original data source

timestampstringRequiredformat: "date-time"

When the identity verification completed, in ISO 8601 format. Use the timestamp from your verification provider's response.

verification_providerstringRequired

Which verification provider verified those attributes for the person or company. If this is an internal process, mention the name of your company.

verified_datalist of objectsRequired

Do not include:

Data points from other verification events
Aggregated results from multiple verifications
Data that wasn’t actually verified in this specific check

Example: If this verification only checked name and DOB, only include those two items in the array, even if other data points were verified in previous or separate verification events.

Array of individual data points verified in this verification event only. Each item represents a specific piece of information (name, DOB, address, etc.) that was checked during this particular verification. Do not include: - Data points from other verification events - Aggregated results from multiple verifications - Data that wasn't actually verified in this specific check Example: If this verification only checked name and DOB, only include those two items in the array, even if other data points were verified in previous or separate verification events.

related_company_idstringOptional

Unique identifier of the related company entity (used for business contexts). Only one of related_company_id and related_person_id can be specified.

related_person_idstringOptional

Unique identifier of the related person entity (used for retail contexts or when a person is the subject). Only one of related_company_id and related_person_id can be specified.

verification_overall_outcomestringOptional

Result of IDV screening returned from provider

verification_typeenumOptional

Allowed values:

Response

Identity verifications updated successfully

successboolean

Indicates if the write operation was successful.

write_countinteger

The number of records written to the database.

messagestring

Provides additional information about the operation result.

organization_idstring

The organization ID for which the operation was performed.

1	import requests
2
3	url = "https://api.cable.tech/v2/identity_verification"
4
5	payload = [
6	{
7	"verification_id": "string",
8	"timestamp": "2024-01-15T09:30:00Z",
9	"verification_provider": ["Middesk", "Socure", "OneFootPrint", "RightTrue", "Cognito"],
10	"verified_data": [
11	{
12	"type": ["name", "dob", "document", "id_number", "address", "tin"],
13	"outcome": "string"
14	}
15	]
16	}
17	]
18	headers = {
19	"Authorization": "Bearer <token>",
20	"Content-Type": "application/json"
21	}
22
23	response = requests.put(url, json=payload, headers=headers)
24
25	print(response.json())

1	{
2	"success": true,
3	"write_count": 1,
4	"message": "string",
5	"organization_id": "string"
6	}

Authentication

Request

Response

Errors