Skip to main content

Identify Users

The identify endpoint links user traits (such as email, name, plan, and company) to a distinct_id. Once identified, these traits appear alongside events in the Chippy Analytics dashboard, enabling segmentation and cohort analysis.

POST /api/v1/identify

Request Body

Example Request

Response

202 Accepted

Error Responses

400 Bad Request: missing traits:
401 Unauthorized: invalid API key:

Common Traits

You can send any key-value pairs as traits. The following are commonly used and have built-in support in the Chippy Analytics dashboard:
Custom traits beyond this list are fully supported. Any key-value pair you send will be stored and available for filtering in the dashboard.

When to Call Identify

Call the identify endpoint at key moments in the user lifecycle to keep traits current:
  • On signup: set initial traits like email, name, plan, and created_at.
  • On login: refresh traits in case they changed since the last session.
  • When the user profile changes: update specific traits such as plan after an upgrade, or company after an org change.
You do not need to send every trait on every call. Chippy merges new traits with existing ones, so you can send only the fields that changed.

Example: Updating a single trait after a plan upgrade

Each identify call creates a special $identify event internally. This means you can see exactly when user traits were set or updated in your event timeline.