Vero API

Name: Vero API API
Brand: Vero API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey18 EndpointsREST

For Agents

Identify users, track events, manage tags, and create or launch campaigns through the Vero marketing-automation API across 18 endpoints with query-token authentication.

Connect the Vero API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vero 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 API API.

Identify users with traits to populate Vero campaign targeting

Alias an anonymous user identifier to a known canonical user id

Track events on a user record to drive lifecycle automations

Create, list, and update marketing campaigns

GET STARTED

Start building with Vero API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Vero API, keeping it validated and agent-ready. The Vero API is the full marketing-automation surface combining user identification, event tracking, tag management, and campaign control. Across 18 endpoints it covers user identify and alias, event tracking, campaign list and create, campaign launch, trigger handling, and message and tag operations. Authentication is an authToken passed as a query parameter, matching the Track REST API's pattern.

Use Cases

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

★ Programmatic Campaign Launch from a Workflow Tool

Marketing-ops teams want a workflow tool to launch a Vero campaign once an upstream event fires (e.g. trial start, billing change). POST /campaigns/{id}/launch accepts the campaign id and triggers delivery to its configured audience. Combined with GET /campaigns the system can find the right campaign by name or status before launching.

List campaigns with status 'ready', find the one named 'Trial Day 7', and launch it via POST /campaigns/{id}/launch.

Identity Stitching with Alias

Web analytics tracks anonymous visitors before they sign up. When the user creates an account, POST /users/alias links the anonymous id to the new canonical user id so all events and tags collected pre-signup follow them into the marketing record. This avoids losing pre-signup behaviour data when targeting.

Alias anonymous id 'anon_482' to user id 'usr_482' and identify that user with email 'a@example.com'.

Campaign Creation from Templates

Marketing teams that template campaigns (e.g. 'Trial Day N' for products with multiple plans) can use POST /campaigns to spin up new campaigns from a stored configuration. PATCH /campaigns/{id} updates campaign settings as the team iterates on copy or audience without recreating the campaign record.

Create a campaign named 'Q3 Win-Back' with the saved template id and report the new campaign id.

AI Agent Marketing Operations

An AI agent monitoring product signals can identify users, edit tags, create campaigns, and launch them when conditions are met — all without UI navigation. Through Jentic the agent finds each operation by intent ('launch a vero campaign', 'tag a user') and Vero's authToken stays in the encrypted vault rather than being passed in as a query string the agent can see.

Identify user 'usr_555', tag them 'high-intent', then launch campaign id 'camp_high_intent_2026'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/users/identify

Identify or update a user with traits

POST

/users/alias

Alias an anonymous id to a canonical user id

POST

/track

Track an event for a user

GET

/campaigns

List campaigns

POST

/campaigns

Create a campaign

POST

/campaigns/{id}/launch

Launch a campaign

PATCH

/campaigns/{id}

Update a campaign

POST

/tags/edit

Add or remove tags on a user

POST

/users/identify

Identify or update a user with traits

POST

/users/alias

Alias an anonymous id to a canonical user id

POST

/track

Track an event for a user

GET

/campaigns

List campaigns

POST

/campaigns

Create a campaign

POST

Why though Jentic?

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

Credential isolation

Vero authToken values are stored encrypted in the Jentic vault. Agents receive a scoped invocation capability, which is critical because Vero passes the token as a URL query parameter — without Jentic the token would otherwise leak to access logs.

Intent-based discovery

Agents search by intent (e.g. 'launch a vero campaign' or 'alias an anonymous user') and Jentic returns the matching operation with its full input schema for direct execution.

Time to first call

Direct Vero integration including auth, identify/alias logic, and campaign management wiring: 2-3 days. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Vero Track REST API

The Track REST API is the lighter ingestion-only subset; the full Vero API also covers campaigns

Use the Track REST API for pure event ingestion; use the full Vero API when the workflow also creates or launches campaigns

Alternative

Customer.io

Customer.io is a comparable marketing-automation platform with similar identify, track, and campaign APIs

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

Alternative

Mailchimp

Mailchimp is a comparable email marketing platform with broader audience and template tooling

Use Mailchimp when broad email marketing tools and templates matter; choose Vero for behavioural lifecycle automation

FAQs

Specific to using Vero API API through Jentic.

Why is there no official OpenAPI spec for Vero API?

Vero does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Vero 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 API use?

Vero uses an apiKey scheme — the authToken is passed as a query parameter on every request. Through Jentic this token is stored encrypted in the vault and the agent receives a scoped invocation capability, which avoids leaking the token in URL query strings to client logs.

Can I launch a campaign with the Vero API?

Yes. POST /campaigns/{id}/launch accepts the campaign id and triggers delivery to the campaign's configured audience. List campaigns first via GET /campaigns to confirm the campaign id and status before launching.

What are the rate limits for the Vero API?

The spec does not declare specific rate limits. Vero's track surface is high-throughput; campaign mutation endpoints have lower limits. Production integrations should implement exponential backoff on 429 responses, especially around bulk identify or campaign create runs.

How do I create a campaign through Jentic?

Search Jentic for 'create a vero campaign'. Jentic returns POST /campaigns with its input schema; load it with the campaign config (name, template, audience), execute, and capture the returned campaign id for follow-up operations.

Can I link an anonymous user to a known user with the Vero API?

Yes. POST /users/alias maps an anonymous id to a canonical user id so events and tags collected pre-signup follow the user into the identified record. Run it once at signup time before subsequent identify or track calls.