IntegrationIngest API
POST /track
POST /api/ingest/track
Authorization: Bearer jk_live_…
Content-Type: application/jsonBody
One event:
{
"contactId": "user-123",
"event": "subscription_started",
"properties": { "plan": "pro", "mrr": 49 },
"timestamp": "2026-09-01T12:00:00Z"
}or a batch:
{ "events": [ { "contactId": "…", "event": "…" }, … ] }| Field | Type | |
|---|---|---|
contactId | string (1–255) | Required. Your id for the person. Created on first sight. |
event | string (1–120) | Required. Letters, digits, _ . : -. |
properties | object | Any JSON. Default {}. |
timestamp | ISO 8601 string | When it happened. Default: now. Secret keys only. |
Batches hold 1–500 events and may mix contacts.
Response
202 Accepted
{ "accepted": 1 }Contacts and events are stored before the response; workflow matching and goal tracking happen asynchronously.
Events are unlimited on every plan. Plans limit contacts and workflow emails per calendar month, and those limits are soft: going over never drops events or stops emails, it sends the workspace owners an email asking them to upgrade.
What happens next
- Every referenced contact is upserted (created, or last seen bumped).
- Events are stored. Names that have no definition appear as Undefined in Workflows → Event definitions.
- Active workflows triggered by this event are matched (audience checked, one run per contact); goal events are recorded on open runs.
Example
curl -X POST https://journeykit.io/api/ingest/track \
-H "Authorization: Bearer jk_live_…" \
-H "Content-Type: application/json" \
-d '{
"events": [
{ "contactId": "user-123", "event": "trial_started", "properties": { "plan": "pro" }, "timestamp": "2026-08-20T09:00:00Z" },
{ "contactId": "user-123", "event": "subscription_started", "properties": { "plan": "pro", "mrr": 49 } }
]
}'