Skip to main content
Get a customer by ID
curl --request GET \
  --url https://api.spherepay.co/v2/customer/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "customer_f31121c389624d3697cbf3ea8830b7a4",
  "verificationProfiles": [
    {
      "name": "kyc_profile_a",
      "status": "incomplete",
      "criteria": {
        "complete": [
          "email_address",
          "phone_number",
          "residential_address",
          "tax_identification_number"
        ],
        "pending": [],
        "required": [
          "identity_document",
          "liveness_report_document"
        ],
        "errors": []
      }
    }
  ],
  "tosStatus": "incomplete",
  "createdAt": "2026-03-09T20:46:31.305Z",
  "updatedAt": "2026-03-09T20:46:31.305Z",
  "type": "individual",
  "email": "jane.smith@example.com",
  "phone": "+14155550123",
  "meta": {},
  "firstName": "Jane",
  "lastName": "Smith",
  "dateOfBirth": "1990-01-15",
  "personalInformation": {
    "taxIdentificationNumberType": "ssn",
    "taxIdentificationNumberCountry": "USA",
    "taxIdentificationNumberDescription": "<string>",
    "gender": "male",
    "countryOfBirth": "USA",
    "nationality": "USA",
    "middleName": "James",
    "occupationSocCode": "15-1132",
    "residencyCountry": "USA",
    "sourceOfFunds": "salary"
  }
}
Use this endpoint to fetch the full details of a single customer by their unique ID. The response includes the customer’s current verification profile status, which tells you exactly which KYC/KYB criteria remain outstanding before the customer can initiate a transfer. You can also inspect attached bank accounts and wallets through this record.

Authorizations

​
Authorization
string
header
required

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

Path Parameters

​
id
string
required

Customer ID

Example:

"customer_f31121c389624d3697cbf3ea8830b7a4"

Response

Response containing information about an individual customer.

​
id
string
required

Customer ID

Example:

"customer_f31121c389624d3697cbf3ea8830b7a4"

​
verificationProfiles
object[]
required

Array of verification profiles. For individual customers, this will include kyc_profile_a. For business customers, this will include kyb_profile_a. See KYC Flow for individuals or KYB Flow for businesses. See Verification Profile for individual status definitions and criteria breakdown or Verification Profile for business status definitions and criteria breakdown.

Example:
[
  {
    "name": "kyc_profile_a",
    "status": "incomplete",
    "criteria": {
      "complete": [
        "email_address",
        "phone_number",
        "residential_address",
        "tax_identification_number"
      ],
      "pending": [],
      "required": [
        "identity_document",
        "liveness_report_document"
      ],
      "errors": []
    }
  }
]
​
tosStatus
enum<string>
required

Customer Terms of Service acceptance status (incomplete | pending | approved).

Available options:
incomplete,
pending,
approved
Example:

"incomplete"

​
createdAt
string
required

ISO 8601 formatted customer creation timestamp

Example:

"2026-03-09T20:46:31.305Z"

​
updatedAt
string
required

ISO 8601 formatted customer update timestamp

Example:

"2026-03-09T20:46:31.305Z"

​
type
enum<string>
required

Customer type

Available options:
individual
Example:

"individual"

​
email
string

Customer email address

Example:

"jane.smith@example.com"

​
phone
string

Customer phone number

Example:

"+14155550123"

​
meta
object
​
firstName
string

Customer first name (individual customers only)

Example:

"Jane"

​
lastName
string

Customer last name (individual customers only)

Example:

"Smith"

​
dateOfBirth
string

The customer's date of birth in YYYY-MM-DD format (individual customers only).

Example:

"1990-01-15"

​
personalInformation
object

Personal information for an individual customer, echoed back from the most recent submission. The tax identification number is omitted from responses for privacy.

Last modified on June 18, 2026