Skip to main content
GET
/
identities
/
:id
curl -X GET https://YOUR_BLNK_INSTANCE_URL/identities/idt_1234567890 \
  -H "X-Blnk-Key: YOUR_API_KEY"
{
  "identity_id": "idt_1234567890",
  "identity_type": "individual",
  "first_name": "John",
  "last_name": "Doe",
  "other_names": "",
  "gender": "male",
  "email_address": "john.doe@example.com",
  "phone_number": "+1234567890",
  "nationality": "US",
  "organization_name": "",
  "category": "individual",
  "street": "123 Main St",
  "country": "United States",
  "state": "California",
  "post_code": "90210",
  "city": "Beverly Hills",
  "dob": "1990-01-15T00:00:00Z",
  "created_at": "2024-01-15T10:30:00Z",
  "meta_data": {
    "customer_tier": "premium"
  }
}
Retrieves detailed information about a specific identity using its unique identifier. If fields have been tokenized, they will be returned in their tokenized form.

Path Parameters

id
string
required
The unique identifier of the identity to retrieve

Response

identity_id
string
Unique identifier for the identity
identity_type
string
Type of identity (e.g., “individual”, “organization”)
first_name
string
First name (may be tokenized if PII protection is enabled)
last_name
string
Last name (may be tokenized if PII protection is enabled)
other_names
string
Other names (may be tokenized if PII protection is enabled)
gender
string
Gender
email_address
string
Email address (may be tokenized if PII protection is enabled)
phone_number
string
Phone number (may be tokenized if PII protection is enabled)
nationality
string
Nationality
organization_name
string
Organization name
category
string
Category classification
street
string
Street address (may be tokenized if PII protection is enabled)
country
string
Country
state
string
State or province
post_code
string
Postal code (may be tokenized if PII protection is enabled)
city
string
City
dob
string
Date of birth in ISO 8601 format
created_at
string
Timestamp when the identity was created
meta_data
object
Additional metadata including tokenization tracking information
curl -X GET https://YOUR_BLNK_INSTANCE_URL/identities/idt_1234567890 \
  -H "X-Blnk-Key: YOUR_API_KEY"
{
  "identity_id": "idt_1234567890",
  "identity_type": "individual",
  "first_name": "John",
  "last_name": "Doe",
  "other_names": "",
  "gender": "male",
  "email_address": "john.doe@example.com",
  "phone_number": "+1234567890",
  "nationality": "US",
  "organization_name": "",
  "category": "individual",
  "street": "123 Main St",
  "country": "United States",
  "state": "California",
  "post_code": "90210",
  "city": "Beverly Hills",
  "dob": "1990-01-15T00:00:00Z",
  "created_at": "2024-01-15T10:30:00Z",
  "meta_data": {
    "customer_tier": "premium"
  }
}

Tokenized Fields

When fields are tokenized, they are stored in a format-preserving encrypted format (prefixed with FPT:):
  • The tokenized value maintains the same character types (letters, numbers, special characters)
  • Original values can only be retrieved using the detokenization endpoints
  • The meta_data.tokenized_fields object tracks which fields are currently tokenized

Build docs developers (and LLMs) love