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.

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

Yes. Jentic One is self-hosted, so your own rules decide which Vero operations the agent may call and which credentials it may use. Because Vero puts the campaign id in the URL path (/campaigns/{id}/launch and /campaigns/{id}), you can pin the agent to a single campaign for launch and update. You choose the operations it may call, so broader ones like identifying users through /users/identify or editing tags through /tags/edit are excluded unless you add them.