Skip to main content
GET
Get a contact

Authorizations

Authorization
string
header
required

Send either an API token or an OAuth access token as Authorization: Bearer <token>. See the Authentication page for details.

Headers

Privy-Account-Id
string

Target a subaccount instead of the main connected account. Pass a subaccount id from get_account's subaccounts list. Only direct subaccounts of the connected account are reachable — omit this for the main account itself.

Path Parameters

id
string
required

The contact's unique identifier (returned as id in contact responses). Ids are opaque cus_-prefixed strings — a numeric id from a Privy dashboard URL is not a valid API id and will 404; list contacts, or look the contact up by ?email= or ?phone_number=, instead.

Response

The requested contact.

data
object

A contact in your Privy account: identity, marketing consent per channel, tags, and custom fields. Email and SMS consent are tracked independently — a contact who opts out of one keeps whatever consent they had for the other.