canonical: https://jentic.com/apis/getvero.com/vero-track-rest-api

# Getvero Vero Track REST API

Jentic publishes the only available OpenAPI specification for Vero Track REST API, keeping it validated and agent-ready. The Track REST API is Vero's user and event tracking surface used by the marketing-automation engine to drive lifecycle messaging. Across 7 endpoints it covers user identification and re-identification, subscription state changes, tag editing, user deletion, and event tracking. The API is stable - v2.0 has been in production since before 2016 with no breaking changes - and authentication is an auth_token query parameter.

## For AI agents

Track users and events, manage subscription state, and edit user tags in Vero across 7 stable endpoints with auth_token query authentication.

## Scope

Does not handle campaign creation, message rendering, or analytics dashboards - use for Vero user identification, event tracking, and subscription/tag updates only.

## Capabilities

- Identify users with traits so Vero can address them in lifecycle campaigns
- Track product or marketing events tied to a user identifier
- Unsubscribe or resubscribe users from messaging programmatically
- Edit a user's tags to add or remove segment membership
- Delete a user from Vero in response to a deletion request
- Re-identify a user by mapping an old id to a new canonical id

## Use cases

### Product Event Tracking for Lifecycle Campaigns

Product and growth teams send events such as 'signed up', 'completed checkout', or 'abandoned cart' to Vero so the lifecycle engine can trigger the right email at the right moment. POST `/events/track` records the event with a user identifier and arbitrary properties, allowing Vero campaigns to branch on those properties when sending.

Example prompt: Track an event named 'completed-checkout' for user id 'usr_123' with properties {order_id:'o-987', total:49.99}.

### Subscription State Management

When a user clicks unsubscribe in an email or asks support to remove them from messaging, an integration calls POST `/users/unsubscribe` to update Vero's subscription state. POST `/users/resubscribe` restores messaging when the user opts back in. This keeps Vero's source of truth aligned with the user's stated preferences.

Example prompt: Unsubscribe user id 'usr_456' from Vero and confirm a 200 response.

### Tag-Based Segmentation Updates

Marketing teams use Vero tags to drive segment membership for campaigns. PUT `/users/tags/edit` lets a system add or remove tags in response to upstream events - for example tagging a user 'trial-day-7' or removing 'free-tier' once they upgrade - so the right campaign fires without manual list management.

Example prompt: Add tag 'enterprise-trial' and remove tag 'self-serve' for user id 'usr_789'.

### AI Agent Lifecycle Coordination

An AI agent observing product events can record them in Vero, update tags, and toggle subscription state without UI navigation. Through Jentic the agent finds the right operation by intent ('track an event in vero', 'unsubscribe a user') and executes - Vero's auth_token stays in the encrypted vault rather than reaching the agent.

Example prompt: Track event 'demo-completed' for user 'usr_999', then add the tag 'ready-for-sales-followup' to that user.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/users/track` | Identify or update a user with traits |
| POST | `/users/unsubscribe` | Unsubscribe a user from messaging |
| POST | `/users/resubscribe` | Resubscribe a user to messaging |
| POST | `/users/delete` | Delete a user from Vero |
| PUT | `/users/reidentify` | Re-identify a user with a new canonical id |
| PUT | `/users/tags/edit` | Add or remove tags on a user |
| POST | `/events/track` | Track an event for a user with properties |

## Key resources

- **Users** — Identify, re-identify, delete, unsubscribe, and resubscribe users
- **Tags** — Add or remove tags on a user record
- **Events** — Track product or marketing events tied to a user

## Why Jentic

- **Setup:** Wiring the Vero Track REST API by hand means appending your auth_token to the query string on every request to api.getvero.com, and keeping that token out of your own logs yourself. Through Jentic you install once, import the Vero Track REST API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Vero Track identifies the user in the request body rather than the URL path, so scope the agent to the operations it needs, such as tracking an event or updating tags. You choose the allowed operations, so actions like deleting or unsubscribing a user are only available if you include them.
- **Credential handling:** Your Vero auth_token is stored once, encrypted, by your own Jentic One instance and injected at execution time, which matters because it rides in the query string. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'track an event in Vero' or 'unsubscribe a user', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Vero API** — The full Vero API adds campaign management on top of the Track REST API's user/event surface
- **Customer.io** — Customer.io is a comparable lifecycle marketing platform with track and campaign APIs
- **Segment** — Segment fans out a single track call to Vero alongside other marketing tools

## FAQ

### Why is there no official OpenAPI spec for Vero Track REST API?

Vero does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Vero Track REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Vero Track REST API use?

Vero Track uses an apiKey scheme - the auth_token is passed as a query parameter on every request. Through Jentic this token lives in the encrypted vault; the agent receives a scoped invocation capability so the raw token never enters its context.

### Can I track an event with the Vero Track REST API?

Yes. POST `/events/track` accepts an identity (user id and email), an event name, and arbitrary event properties. Vero records the event against the user record so lifecycle campaigns can branch on it.

### What are the rate limits for the Vero Track REST API?

The spec does not declare specific rate limits. Vero's documented guidance is that the Track API is high-throughput for ingestion; production senders should batch where possible and implement exponential backoff on 429 responses.

### How do I unsubscribe a user from Vero through Jentic?

Search Jentic for 'unsubscribe a user from vero'. Jentic returns POST `/users/unsubscribe` with its input schema; load it with the user identifier and execute. The response confirms the subscription state change.

### Can I edit a user's tags in Vero?

Yes. PUT `/users/tags/edit` accepts the user identifier plus add and remove arrays for tag names. Vero updates the user's tag set in one call so segment membership changes atomically.

### Can I limit what my agent is allowed to do with the Vero Track API?

Yes. Because you run Jentic One yourself, your own rules decide which Vero Track operations and credentials the agent may use. You can allow only the endpoints a task needs, such as POST `/events/track` or PUT `/users/tags/edit`, while withholding destructive ones like POST `/users/delete` or POST `/users/unsubscribe` unless you explicitly include them. Since Vero identifies the user in the request body rather than the URL path, scoping is done per operation, and the stored auth_token is injected at execution time so it never reaches the agent.