Skip to main content
This guide takes you from zero to a working integration: an API key, a successful call, and a webhook delivery you can inspect.
Every ID in this guide (aut_..., whk_..., evt_..., lea_..., agt_...) is an opaque, prefixed string — never a UUID, and never something you parse or validate.

Prerequisites

  • curl (or any HTTP client)
  • Node.js and npx, to run a local mock of the contract
  • A browser, to open a webhook.site URL

Start a local mock

The real API doesn’t serve webhooks yet (see the availability note on each reference page), so this guide runs against a mock generated straight from this repository’s own contract file — the exact same one the API Reference tab is built from.
This starts a server on http://127.0.0.1:4010 that answers every route in the contract with its documented examples. Leave it running in a terminal, and follow the steps below in another one.

Get started

1

Create your API key

In your Agentova workspace, go to Settings → API and create a key. It looks like agk_live_<32 characters> — one key gives you access to the entire workspace, there’s no per-key scoping in v1.
Keep this key secret. Anyone with it has full read/pause/activate access to your workspace’s automations.
2

Make your first call

GET /automations doubles as a connection test — call it with limit=1:
A working key returns a paginated list:
A missing or revoked key returns 401 invalid_api_key instead — see Errors.
3

Open a receiver for your first webhook

Go to webhook.site and copy the unique URL it gives you. You’ll use it as the subscription target — no server of your own required for this guide.
4

Subscribe to an event

The response includes a secretshown only once, it’s what you’d use to verify the X-Agentova-Signature header on real deliveries:
5

See a delivery arrive

The mock doesn’t fire real deliveries yet (no persistence, no background jobs) — so to see the exact shape of what a lead.created delivery looks like, send the contract’s own example straight to your webhook.site URL:
Refresh the webhook.site page — you’ll see the request land, headers and body intact. On a real delivery, the signature would be computed from your subscription’s own secret; see Webhooks & signatures for how to verify it yourself.

Next steps

Pagination

How cursors work across every list endpoint.

Errors

The full list of error codes and how to handle them.

Rate limits

Headers on every response, and what happens past the quota.

API Reference

Every endpoint, generated straight from the contract.