Skip to main content
POST
/
customers
/
{id}
/
identifications
Create customer identification
curl --request POST \
  --url https://api.sandbox.iron.xyz/api/customers/{id}/identifications \
  --header 'Content-Type: application/json; charset=utf-8' \
  --header 'IDEMPOTENCY-KEY: <idempotency-key>' \
  --header 'X-API-Key: <api-key>' \
  --header 'X-SUB-PARTNER-ID: <x-sub-partner-id>' \
  --data '
{
  "type": "Direct"
}
'
{
  "created_at": "2023-11-07T05:31:56Z",
  "customer_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "Pending",
  "updated_at": "2023-11-07T05:31:56Z",
  "step_status": {
    "company_beneficiaries": {
      "result": "Pending",
      "retry": true
    },
    "company_data": {
      "result": "Pending",
      "retry": true
    },
    "company_documents": {
      "result": "Pending",
      "retry": true
    },
    "questionnaire": {
      "result": "Pending",
      "retry": true
    }
  },
  "url": "<string>"
}

Authorizations

​
X-API-Key
string
header
required

API Key

Headers

​
IDEMPOTENCY-KEY
string
required

a UUID ensuring an Customer Identification operation is only processed once

​
X-SUB-PARTNER-ID
string
required

Optional sub-partner UUID, if provided, the identification will be created under scope of the sub-partner

Path Parameters

​
id
string<uuid>
required

the ID of the Customer to create an Identification for

Body

application/json; charset=utf-8

The Identification data to be used for the identification

  • IdentDirectParams
  • OutsourcedPersonParams
  • OutsourcedBusinessParams
  • ReliancePersonParams

Identification Create Params

The params required to create an identification, we support two types of identification:

  • Outsourced: where data is provided in the request
  • Direct: where we will trigger a verification using our providers built in flows for data collection
  • Reliance: where a token is provided in the request from which verification data can be extracted
​
type
enum<string>
required
Available options:
Direct
Example:

"Direct"

Response

POST Customer Identification Succeeded

Identification

The entity wrapping our KYC/KYB process and underlying providers

​
created_at
string<date-time>
required
​
customer_id
string<uuid>
required
​
id
string<uuid>
required
​
status
enum<string>
required

The Process status of the identification

The various state transitions an identification can go through.

Available options:
Pending,
Processed,
PendingReview,
Approved,
Declined,
Expired
​
updated_at
string<date-time>
required
​
step_status
BusinessIdentificationStepStatus · object
  • BusinessIdentificationStepStatus
  • PersonIdentificationStepStatus
​
url
string