---
title: "Track event"
method: POST
path: "/track"
tags: ["Track"]
---

# Track event

`POST /track`

Endpoint used to track an event for a user or an account.

## Request body

- object — Event for a user or an account
  - `identification` object, required — Event identification requires a user, account or both
    - `account` object — Account identification requires an accountId, domain or both
      - `domain` string, top-level-domain — The domain associated with the account (e.g. acme-inc.com)
      - `accountId` string, account-id — Unique identifier for the account in your database
    - `user` object — User identification requires a userId, email or both
      - `email` string, email — Email address of the user
      - `userId` string, user-id — Unique identifier for the user in your database
  - `name` string, event-name, required
  - `metadata` object — Event metadata, possible values are strings, booleans, numbers and datetimes (ISO 8601)
  - `triggeredAt` string, datetime — If left blank this defaults to the current datetime

## Response `201`

Object was created

- object — The message specifies what is done
  - `meta` object, required
    - `requestId` string, required
    - `status` number, required
  - `message` string, required

## Other responses

- `400` — Bad request, some fields or parameters are incorrect
- `401` — No API Key was provided or the key is not authorised to perform the action
- `403` — The API Key provided is currently not enabled
- `429` — Too many API requests were send
- `500` — An unexpected error occurred

---

[API](https://skmtc.dev/journy/apis/developer-documentation.md) · [All operations](https://skmtc.dev/journy/apis/developer-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/journy/developer-documentation/revisions/2abe45a5c780/schema)