curl --request POST \
--url https://api.mailglyph.com/v1/track \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"email": "[email protected]",
"event": "purchase",
"data": {
"product": "Premium Plan",
"amount": 99
}
}
'{
"success": true,
"data": {
"contact": "<string>",
"event": "<string>",
"timestamp": "2023-11-07T05:31:56Z"
}
}Events
Track event
Track an event for a contact. Automatically creates/updates the contact.
POST
/
v1
/
track
curl --request POST \
--url https://api.mailglyph.com/v1/track \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"email": "[email protected]",
"event": "purchase",
"data": {
"product": "Premium Plan",
"amount": 99
}
}
'{
"success": true,
"data": {
"contact": "<string>",
"event": "<string>",
"timestamp": "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.
Body
application/json
Contact email
Event name
Whether contact is subscribed to marketing emails. Defaults to true for event tracking.
Optional event data and contact metadata. Choose Empty object if you do not want to send any example preset keys.
- Example object
- Empty object
Show child attributes
Show child attributes
Example:
{ "product": "Premium Plan", "amount": 99 }