API keys and webhooks

Everything in Vetta is accessible programmatically: records, pipelines, tasks, notes, metadata. API keys authenticate your integrations, and webhooks push events to your systems in real time. They are the two building blocks for connecting Vetta to your own tools and scripts.

Both live in Settings > Integrations: APIs and Webhooks. Full endpoint documentation is in the API Reference.

API keys

An API key is a bearer token that authenticates requests to Vetta's APIs.

Creating one:

1. Go to Settings > Integrations > APIs
2. Click Create API key
3. Give it a Name and an Expiration Date (15 days, 30 days, 90 days, 1 year, 2 years or Never; Never by default), then click Save at the top right
4. Copy the key immediately and keep it somewhere safe: it's shown once and can't be retrieved later. If you lose it, you have to regenerate it and update everything that uses it

Narrated video · 0:54

Creating an API key to connect Vetta to your own tools. In Settings, open Integrations, then APIs, and click Create API key. Name it after what will use it, choose when it expires (fifteen days, thirty, ninety, a year, two years or never) and Save. Copy it now, because it is shown only once; if lost, regenerate it and update everything that uses it. Paste it under Documentation, choose REST or GraphQL and click Launch to try it.

Transcript

To connect Vetta to your own tools, you need an API key. In Settings, open Integrations, then APIs, and click Create API key. Name it after what will use it, like your CRM sync, so you always know which key does what. Then pick when it expires: fifteen days, thirty, ninety, a year, two years, or never. Click Save, and the key appears. Copy it now and keep it somewhere safe, because it's only shown this once. If you lose it, you'll have to regenerate it and update everything that uses it. To try it out, paste the key under Documentation, choose REST or GraphQL, and click Launch. REST opens a reference of every endpoint, already authorised with your key. GraphQL opens an editor, so you can run a query and see your workspace data straight away.

Managing keys:

• Regenerate Key: invalidates the old value and issues a new one for the same key entry; update your integrations with the new value
• Delete API key: revokes access entirely (in the key's Danger zone)

Good practice: one key per integration, named accordingly ("Zapier", "Lead sync script"). When a tool is retired or a key may have leaked, delete or regenerate just that key without breaking everything else. Access to settings is controlled by each member's role.

The APIs

Two interfaces are available:

• REST: CRUD operations on every entity, including custom entities and pipelines (which are discoverable via the metadata endpoints)
• GraphQL: including full-text search across records

Try both live from the built-in playground: under Documentation on the APIs page, paste an API key, choose the Schema (Core or Metadata) and the API (REST or GraphQL), and click Launch. REST opens a reference of every endpoint, already authorised with your key; GraphQL opens an editor where you can run a query against your workspace data straight away. An invalid key shows "Failed to validate API key". It's the fastest way to explore the schema and prototype a query before writing code.

There is no fixed rate limit on the API at the moment. If you plan heavy use, contact support at hello@meetvetta.com and the team will work out the volume that suits you.

Webhooks

Webhooks notify your systems the moment something happens in Vetta, with no polling.

Creating one:

1. Go to Settings > Integrations > Webhooks
2. Click Create Webhook
3. Set the Endpoint URL: Vetta will send POST requests to it for every matching event
4. Choose the events with Filters: pick an entity (or All Entities) and an action (create, update, delete: or All Actions)
5. Optionally set a Secret: a string included with every webhook so your endpoint can verify the request genuinely came from Vetta

Webhooks are included in Vetta's single plan, like everything else.

Common patterns:

• Person created → sync to your billing or product database
• Opportunity updated → post deal changes to a Slack channel via your own handler
• Record deleted → keep an external audit trail

Webhooks vs. workflows

Both react to events; choose by where the logic lives:

• Workflows act inside Vetta (update records, enroll in sequences, run AI steps), and their HTTP Request action covers simple outbound calls
• Webhooks are for your infrastructure: they deliver the raw event to your endpoint and your code decides what happens

The HTTP Request action is also how you bring in data from a provider Vetta has no native connector for, such as Apollo, ZoomInfo or Clay: a workflow with an HTTP Request step (the provider's API URL and key) followed by an Update Record step writes the result into the person, and you run it manually on the people you select. See Data enrichment.

Common questions

Key outcome

API keys and webhooks turn Vetta from an application into a platform: your scripts, products, and internal tools can read and write CRM data securely, and react to changes the moment they happen.