curl --request PATCH \
--url https://api.mailglyph.com/contacts/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"subscribed": true,
"data": {
"firstName": "John",
"lastName": "Doe",
"plan": "premium"
}
}
'{
"id": "<string>",
"email": "[email protected]",
"subscribed": true,
"data": {},
"status": "ACTIVE",
"expiresAt": "2023-11-07T05:31:56Z",
"projectId": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"updatedAt": "2023-11-07T05:31:56Z"
}Contacts
Update contact
Update an existing contact
PATCH
/
contacts
/
{id}
curl --request PATCH \
--url https://api.mailglyph.com/contacts/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"subscribed": true,
"data": {
"firstName": "John",
"lastName": "Doe",
"plan": "premium"
}
}
'{
"id": "<string>",
"email": "[email protected]",
"subscribed": true,
"data": {},
"status": "ACTIVE",
"expiresAt": "2023-11-07T05:31:56Z",
"projectId": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"updatedAt": "2023-11-07T05:31:56Z"
}Authorizations
API Key authentication. Secret keys (sk_*) are required for all endpoints except /v1/track. Public keys (pk_*) only work with the /v1/track endpoint for client-side event tracking. Workspaces can have multiple active keys, and sender-domain operations enforce per-key domain scope when configured.
Path Parameters
Body
application/json
Response
200 - application/json
Contact updated
Unique contact identifier
Contact email address
Subscription status
Custom contact data fields
Available options:
ACTIVE, PENDING