---
title: "Track Events"
method: POST
path: "/v1/track"
---

# Track Events

`POST /v1/track`

## Headers

- `Content-Type` string
- `Accept` string
- `Authorization` string, required

## Request body

- object
  - `user_id` string, required — The unique identifier for the user. This is the ID that Userpilot uses to identify the user.
  - `event_name` string, required — Name of the event being tracked. Use descriptive names like 'schedule_appointment', 'purchase_completed', etc.
  - `metadata` object — Optional event metadata. You can add, remove, or modify any properties as needed for your use case.
    - `custom_event_property` string — example: Date and time of the appointment, Product name, etc.

## Response `202`

Accepted - Event tracking successful

## Other responses

- `400` — Bad Request - Invalid input
- `401` — Unauthorized - Invalid API key

---

[API](https://skmtc.net/userpilot/apis/userpilot-api.md) · [All operations](https://skmtc.net/userpilot/apis/userpilot-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/userpilot/userpilot-api/versions/2b3a88b6a474/schema)