Creates an address book recipient. Required fields depend on your Circle entity; use the request body options that match your integration.
Validation failures can return error codes in the 2024–2037 range (for example 2024 when identity is required but missing, 2025 when ownership is required but missing).
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
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"
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.
Related validation error codes include 2024 (identity missing), 2031–2034, and 2036 (identity cannot be updated via PATCH).
Successfully created an address book recipient.
For Circle entities other than CIRCLE_SG.