/api/external/contacts/
Request body
string
required
Contact display name.
string
Sub-org that owns the contact.
string
required
Destination address on the selected chain.
string
required
REST field. The SDK accepts this as
chain.string[]
Searchable contact tags.
string
Client-controlled reference.
string[]
Assets permitted for the contact. The SDK serializes an omitted value as an empty array.
string[]
Organization-scoped contact groups to attach.
Response
Returns the new Contact withstatus: "PENDING".
string
Contact ID.
string
Organization that owns the contact.
string
Contact display name.
string
Chain of the address.
string
Blockchain address.
ContactStatus
PENDING, APPROVED, or DECLINED. A new contact stays PENDING until it’s approved. See ContactStatus.boolean
Whether the address is a smart contract.
string[]
Searchable contact tags.
string
User or API user that created the contact.
boolean
Whether the address is flagged by sanctions screening.
string
Your own reference, if you set one.
string[]
Assets permitted for the contact.
string
Creation timestamp (ISO 8601).
string
Last update timestamp (ISO 8601).
boolean
Whether the contact is deleted.
Approve the contact
A new contact comes back withstatus: "PENDING" and needs your API user’s approval. Call Get Approval Message with entityId set to the contact id, sign the message, and send the signature to Submit Approval Action. See Approvals for the full flow.
With the SDK, approve separately or in one call:
REST request body
Response example