Vero

REST API at https://api.getvero.com/api/v2. Resources: users, events, tags, unsubscribes. POST /users/track identifies a user (creates or updates profile: id, email, data object with custom attributes). POST /events/track tracks a behavioral event ({identity: {id/email}, event: 'name', data: {...}}). POST /users/tags/edit adds/removes tags from a user. POST /users/unsubscribe unsubscribes a user from all campaigns. GET /users/exists checks if a user exists. Response: 200 with JSON (stored: true) on success. Simple flat API design; easy to integrate.

Vero is a behavior-triggered lifecycle email platform — campaigns fire based on user events (product actions, time since signup, purchase history) rather than static schedules. For agents, the REST API covers: identifying/updating user profiles (identify), tracking behavioral events (track), managing tags, and unsubscribing users. These calls feed Vero's campaign trigger engine. Suitable for agents in SaaS or ecommerce lifecycle automation where behavioral email is required. API is clean; less full-featured than Iterable or Braze but easier to get started with. Confidence is docs-derived.

Bearer token auth: Authorization: Bearer {auth_token}. Auth token from Vero account settings → Integration. HTTPS enforced. Single auth token per account. No OAuth2 or token scoping. Token rotation via Vero account settings. Simple API key model appropriate for server-side backend integration; do not expose in client-side code.

developers.getvero.com provides the API reference for users and events endpoints. Documentation is minimal but sufficient for the core API surface. Getting started requires a Vero account (free trial available). No official SDK; the simple REST API is straightforward for direct HTTP calls. Integration guides for common platforms (Segment, Heroku). Community support via Vero support email. Fewer resources and community compared to larger competitors.

Standard HTTP status codes with minimal error bodies (status, error message). 401 for invalid token, 400 for missing required fields (id or email for user identify). Event tracking: 200 means event received (async processing for campaign triggers). User identify is upsert — creates new profile if id/email not found. No explicit rate limit documentation; standard rate limiting applies. Vero platform uptime at status.getvero.com. Webhook support for email event callbacks (opens, clicks, bounces, unsubscribes).