🦸‍♂️Customers

API reference for customer-related endpoints

Add a New Customer

To add a new customer to the system, use the authenticated /customer POST endpoint. This will initialise a new customer entity and start KYC verification process. The response contains a verification URL that redirects to our KYC partner's portal for further verification.

Create new customer

post

/customers

Creates new customer and generates a cryptographic challenge to verify ownership of blockchain account

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Idempotency-Keystring · uuidRequired

Idempotency key (UUID)

Content-DigeststringRequired

Content digest

Body

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

externalIdstringRequired

Unique customer ID in a form of an external identifier. This would normally correspond to customer's ID in your system

Responses

201

Successful operation

application/json

400

Invalid request

401

Not authorised

409

Customer already exists

500

Internal error

post

/customers

POST /v1/customers HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000
Content-Digest: text
Content-Type: application/json
Accept: */*
Content-Length: 85

{
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "externalId": "text"
}

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "externalId": "text",
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "status": "initiating",
  "createdAt": "2026-02-25T21:22:15.965Z",
  "updatedAt": "2026-02-25T21:22:15.965Z",
  "challenge": "LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0KTUZZd0VBWUhLb1pJemowQ0FRWUZLNEVFQUFvRFFnQUUzTEw1RldmVFgvL3BJaXNEL0xneFVIT2lxdlFTSUVWTgpGekloOTdLZXBlWk1iZVZsUGd1akZ4Yk5MN2x1ZVhRQnBpUWUzNmZLN0xSbXZNNHdEaWZFTkE9PQotLS0tLUVORCBQVUJMSUMgS0VZLS0tLS0="
}

Customer Entity Updates

Any internal updates to the customer entity will trigger a webhook update event. For details on how to set up and manage webhook subscriptions, please refer to Webhooks.

Blockchain Updates

In order to proceed with customer verification, a challenge needs to be signed and verified (see Blockchain Updates).

Retrieve Customer Entities

To retrieve a list of all customer entities registered for the programme, make a GET request to /customers.

Retrieve customers

get

/customers

Retrieves customers' details

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Responses

200

Successful operation

application/json

idstring · uuidRequired

Unique customer ID

externalIdstringRequired

Unique customer ID in a form of an external ID

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

statusstring · enumRequired

Customer status

Possible values:

createdAtstring · date-timeRequired

Date this customer was created (ISO-8601)

updatedAtstring · date-timeRequired

Date this customer was updated (ISO-8601)

400

Invalid request

401

Not authorised

500

Internal error

get

/customers

GET /v1/customers HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Accept: */*

[
  {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "externalId": "text",
    "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
    "status": "initiating",
    "createdAt": "2026-02-25T21:22:15.965Z",
    "updatedAt": "2026-02-25T21:22:15.965Z"
  }
]

Retrieve an Individual Customer

To retrieve information about an individual customer, make a GET request to /customers/{customerId} with customer ID as a path parameter.

Retrieve customer

get

/customers/{customerId}

Retrieves customer's details

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

customerIdstring · uuidRequired

Unique customer ID

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Responses

200

Successful operation

application/json

idstring · uuidRequired

Unique customer ID

externalIdstringRequired

Unique customer ID in a form of an external ID

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

statusstring · enumRequired

Customer status

Possible values:

createdAtstring · date-timeRequired

Date this customer was created (ISO-8601)

updatedAtstring · date-timeRequired

Date this customer was updated (ISO-8601)

400

Invalid request

401

Not authorised

404

Customer not found

500

Internal error

get

/customers/{customerId}

GET /v1/customers/{customerId} HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Accept: */*

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "externalId": "text",
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "status": "initiating",
  "createdAt": "2026-02-25T21:22:15.965Z",
  "updatedAt": "2026-02-25T21:22:15.965Z"
}

Deactivate a Customer

To deactivate a customer, use a PATCH request to /customers/{customerId}/deactivate. This will also deactivate all associated resources, such as accounts and cards.

Deactivate customer

patch

/customers/{customerId}/deactivate

Deactivates customer and all associated resources

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

customerIdstring · uuidRequired

Unique customer ID

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Idempotency-Keystring · uuidRequired

Idempotency key (UUID)

Responses

200

Successful operation

application/json

idstring · uuidRequired

Unique customer ID

externalIdstringRequired

Unique customer ID in a form of an external ID

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

statusstring · enumRequired

Customer status

Possible values:

createdAtstring · date-timeRequired

Date this customer was created (ISO-8601)

updatedAtstring · date-timeRequired

Date this customer was updated (ISO-8601)

400

Invalid request

401

Not authorised

404

Customer not found

409

Invalid state transition

500

Internal error

patch

/customers/{customerId}/deactivate

PATCH /v1/customers/{customerId}/deactivate HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000
Accept: */*

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "externalId": "text",
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "status": "initiating",
  "createdAt": "2026-02-25T21:22:15.965Z",
  "updatedAt": "2026-02-25T21:22:15.965Z"
}

Reactivate a Customer

To reactivate a previously deactivated customer, use a PATCH request to /customers/{customerId}/activate.

Activate customer

patch

/customers/{customerId}/activate

Activates customer and all associated resources

Authorizations

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Path parameters

customerIdstring · uuidRequired

Unique customer ID

Header parameters

SignaturestringRequired

HTTP message signature

Signature-InputstringRequired

HTTP message signature input

Idempotency-Keystring · uuidRequired

Idempotency key (UUID)

Responses

200

Successful operation

application/json

idstring · uuidRequired

Unique customer ID

externalIdstringRequired

Unique customer ID in a form of an external ID

chainIdstringRequired

Unique customer ID in a form of a valid on-chain address. This would normally correspond to customer's EOA wallet address

Example: eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb

statusstring · enumRequired

Customer status

Possible values:

createdAtstring · date-timeRequired

Date this customer was created (ISO-8601)

updatedAtstring · date-timeRequired

Date this customer was updated (ISO-8601)

400

Invalid request

401

Not authorised

404

Customer not found

409

Invalid state transition

500

Internal error

patch

/customers/{customerId}/activate

PATCH /v1/customers/{customerId}/activate HTTP/1.1
Host: api.offblocks.xyz
Authorization: Bearer YOUR_SECRET_TOKEN
Signature: text
Signature-Input: text
Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000
Accept: */*

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "externalId": "text",
  "chainId": "eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb",
  "status": "initiating",
  "createdAt": "2026-02-25T21:22:15.965Z",
  "updatedAt": "2026-02-25T21:22:15.965Z"
}

PreviousAPI Reference NextAccounts

Last updated 2 years ago

hashtagAdd a New Customer

hashtagCreate new customer

hashtagCustomer Entity Updates

hashtagBlockchain Updates

hashtagRetrieve Customer Entities

hashtagRetrieve customers

hashtagRetrieve an Individual Customer

hashtagRetrieve customer

hashtagDeactivate a Customer

hashtagDeactivate customer

hashtagReactivate a Customer

hashtagActivate customer

Add a New Customer

Create new customer

Customer Entity Updates

Blockchain Updates

Retrieve Customer Entities

Retrieve customers

Retrieve an Individual Customer

Retrieve customer

Deactivate a Customer

Deactivate customer

Reactivate a Customer

Activate customer