canonical: https://jentic.com/apis/getvero.com

# Vero APIs

Vero is a behavioural marketing-automation platform for lifecycle messaging. Its APIs let systems identify users, track product and marketing events, edit tags for segmentation, manage subscription state, and create or launch campaigns. Jentic publishes and maintains the OpenAPI specifications for both the full Vero API and the lighter Vero Track REST API, keeping them validated and ready for AI agents to call.

## For AI agents

An agent can identify and re-identify users, track events, edit tags, and change subscription state in Vero, and on the full API it can also list, create, update, and launch marketing campaigns. This lets an agent coordinate lifecycle messaging end to end, from recording a product signal to firing the campaign it triggers.

## Scope

Use for: Behavioural lifecycle marketing in Vero: identifying users, tracking events, editing tags, managing subscription state, and creating or launching campaigns.

Not supported:
- SMS delivery
- push notifications
- analytics dashboards
- message rendering
- email template design

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Vero API | marketing | 18 | Identify users, track events, manage tags, and create or launch campaigns through the Vero marketing-automation API across 18 endpoints with query-token authentication. |
| Vero Track REST API | marketing | 7 | Track users and events, manage subscription state, and edit user tags in Vero across 7 stable endpoints with auth_token query authentication. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Track events and identify users only, no campaign control | track-api | The Track REST API is the stable ingestion-only subset covering identify, track, tags, and subscription state across 7 endpoints. |
| Create, update, or launch marketing campaigns | vero-api | The full Vero API adds campaign list, create, update, launch, and trigger operations on top of the same user and event surface. |
| Stitch an anonymous visitor to a known user | vero-api | Only the full Vero API exposes POST /users/alias to map an anonymous id to a canonical user id. |

## Cross-API use cases

### Track a product signal, then launch the campaign it triggers

Send a lifecycle event such as trial-day-7 or completed-checkout through the ingestion surface, then find the matching campaign by name or status and launch it to its configured audience. This connects the moment a user acts to the message that goes out.

Example prompt: Track event 'trial-day-7' for user 'usr_123' via the Track REST API, then list campaigns with status 'ready', find 'Trial Day 7', and launch it through the Vero API.

### Keep segmentation and subscription state consistent across both surfaces

Edit a user's tags and update their subscription state when an upstream signal arrives, using whichever surface the workflow already calls. Both APIs share the same user identifier so tag and subscription changes made through one are reflected when the other reads the record.

Example prompt: Add tag 'high-intent' and remove 'free-tier' for user 'usr_789', then unsubscribe user 'usr_456' from all Vero messaging.

## Why Jentic

- **Setup:** Wiring either Vero 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. Once Jentic One is installed, you or your agent can find and add the Vero APIs from the Jentic directory and store the token once for both.
- **Permission scoping:** Because both APIs share one token, your own rules decide which Vero operations the agent may call. You can allow only event tracking and tag edits while withholding campaign launch or user deletion, and the campaign id in the full API's paths lets a rule pin the agent to a single campaign.
- **Credential handling:** Your Vero auth_token is stored 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 on either API.
- **Discovery method:** Agents search the Jentic directory by intent such as 'track an event in Vero' or 'launch a Vero campaign', and Jentic returns the matching operation from the right API with its input schema so the agent calls the correct endpoint without browsing reference docs.

## Related vendors

- **Customer.io** — Comparable behavioural lifecycle marketing platform with identify, track, and campaign APIs.
- **Mailchimp** — Alternative email marketing platform with broader audience and template tooling.
- **Segment** — Customer data platform that can fan a single track call out to Vero alongside other destinations.

## FAQ

### What is the difference between the Vero API and the Vero Track REST API?

The Track REST API is the lighter ingestion-only subset, covering user identification, event tracking, tag editing, and subscription state across 7 stable endpoints. The full Vero API adds campaign list, create, update, launch, and trigger operations on top of that same surface across 18 endpoints. Use the Track REST API when you only need to record data, and the full Vero API when the workflow also manages campaigns.

### Do the two Vero APIs share the same authentication?

Yes. Both use a single Vero auth_token passed as a query parameter on every request, so one credential works across both APIs. Through your own Jentic One instance the token is stored once and reused for whichever operation the agent calls.

### Can an agent work across both APIs in one workflow?

Yes. Because both APIs share the same user identifiers and the same token, an agent can track an event through the Track REST API and then launch the campaign that event triggers through the full Vero API without any separate setup between the two.

### Does Jentic publish official Vero specifications?

Vero does not publish OpenAPI specifications, so Jentic generates and maintains them for both APIs. Each spec is validated against the live API and kept up to date so agents and developers can call Vero through structured tooling.

### Which API should an agent choose for identity stitching?

Use the full Vero API. Its POST /users/alias operation maps an anonymous visitor id to a canonical user id so events and tags collected before signup follow the user into the identified record. The Track REST API does not expose alias.

### Are the Vero APIs stable enough for production use?

The Track REST API is on v2.0 and has been in production since before 2016 with no breaking changes. The full Vero API is on the same version line. Neither spec declares explicit rate limits, so production integrations should batch where possible and back off on 429 responses.