Vero Track REST API

Name: Vero Track REST API API
Brand: Vero Track REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey7 EndpointsREST

For Agents

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

Connect the Vero Track REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vero Track REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Vero Track REST API API.

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

GET STARTED

Start building with Vero Track REST API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Vero Track REST API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Vero Track REST API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for vero track rest api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Vero auth_tokens are stored encrypted in the Jentic vault. Agents receive a scoped invocation capability — the raw token never enters the agent's context, which is critical because the auth_token rides in the URL query string and would otherwise leak to logs.

Intent-based discovery

Agents search by intent (e.g. 'track an event in vero' or 'unsubscribe a user') and Jentic returns the matching operation with its full input schema for direct execution.

Time to first call

Direct Vero Track integration including auth, error handling, and event property modelling: half a day to one day. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Vero API

The full Vero API adds campaign management on top of the Track REST API's user/event surface

Use the Track REST API for ingestion only; switch to the full Vero API when the workflow also needs to manage campaigns

Alternative

Customer.io

Customer.io is a comparable lifecycle marketing platform with track and campaign APIs

Use Customer.io when the customer already runs it; choose Vero for teams standardised on Vero workflows

Complementary

Segment

Segment fans out a single track call to Vero alongside other marketing tools

Use Segment when many destinations need the same events; call Vero directly when only Vero needs the data

FAQs

Specific to using Vero Track REST API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.