Create a recipient
Creates an address book recipient. Required fields depend on your Circle entity; use the request body options that match your integration.
For Singapore (CIRCLE_SG) customers creating a self-hosted (ownership.custody.type = self_hosted) entry, metadata.email is required and the beneficiary PII object matching identity.type (identity.individual or identity.business) is required. The two PII objects are mutually exclusive. For non-regulated jurisdictions the PII objects are accepted if provided but not required.
Validation failures can return error codes in the 2024–2038 range (for example 2024 when identity is required but missing, 2025 when ownership is required but missing, 2038 when metadata.email is missing for a self-hosted entry), as well as the PII-missing errors ADDRESS_BOOK_INDIVIDUAL_PII_MISSING and ADDRESS_BOOK_BUSINESS_PII_MISSING.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
- General customers
- FR customers
- SG customers
For Circle entities other than CIRCLE_SG.
Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests.
"ba943ff1-ca16-49b2-ba55-1057e70ca5c7"
Blockchain network code for the recipient address (address book scope).
ALGO, APTOS, ARB, AVAX, BASE, CELO, ETH, HBAR, NEAR, NOBLE, OP, PAH, POLY, SOL, SUI, UNI, XLM, XRP, ZKS An alphanumeric string representing a blockchain address. Formatting varies by blockchain.
Be sure to preserve the exact formatting and capitalization of the address.
Important: For Ripple (XRP) addresses, only the classic address format is supported (for example, rPEPPER7kfTD9w2To4CQk6UCfuHM9c6GDY).
The x-address format is NOT supported currently (for example, XV5sbjUmgPpvXv4ixFWZ5ptAYZ6PD2q1qM6owqNbug8W6KV).
"0x8381470ED67C3802402dbbFa0058E8871F017A6F"
Recipient metadata. For Singapore (CIRCLE_SG) customers creating a self-hosted (ownership.custody.type = self_hosted) entry, email is required (validation error 2038).
The secondary identifier for a blockchain address. An example of this is the memo field on the Stellar network, which can be text, id, or hash format.
"123456789"
Beneficiary identity for the address book entry.
When type is individual, include firstName and lastName. When type is business, include businessName.
Beneficiary Personally Identifiable Information (PII) required for MAS Travel Rule compliance on self-hosted wallet payouts is carried in the nested individual and business objects. These two child objects are mutually exclusive — at most one may be provided, and it must match type. For Singapore (CIRCLE_SG) customers creating a self-hosted (ownership.custody.type = self_hosted) entry the child object matching type is required; for non-regulated jurisdictions it is accepted if provided but not required. Name fields stay at this level and are not duplicated inside the child objects.
Related validation error codes include 2024 (identity missing), 2031–2034, 2036 (identity cannot be updated via PATCH), and the PII-missing errors ADDRESS_BOOK_INDIVIDUAL_PII_MISSING and ADDRESS_BOOK_BUSINESS_PII_MISSING.
Response
Successfully created an address book recipient.
For Circle entities other than CIRCLE_SG.
- General customers
- FR customers
- SG customers