What we do
Tools
Industries
Department
How we workLet's talk →
Home/ActiveCampaign/ActiveCampaign API
ActiveCampaign

The ActiveCampaign API, from first request to the webhooks that come back

ActiveCampaign's v3 REST API covers contacts, tags, custom fields, deals and lists, and it can start a contact in an existing automation. It can't build or edit the automation itself. Here's how to authenticate, which endpoint fits which job, and the webhook behavior that trips people up.

Before you write any code

Your URL and key are on the Developer settings page. Each user has their own key, and the URL is unique to your account.

Settings Developer

Requests go to https://youraccount.api-us1.com/api/3/... with the key in an Api-Token header. GET /api/3/users/me is a safe first call.

The limit is 5 requests per second per account. Over it, you get a 429 with a Retry-After header saying how many seconds to wait.

Which ActiveCampaign endpoint does the job

What you need to happen Endpoint Worth knowing
Add or update a contact from your app or store POST /api/3/contact/sync Creates the contact if the email is new, updates it if not. Saves you a lookup before every write.
Set a custom field on a contact fieldValues on the contact, or POST /api/3/fieldValues Fields are referenced by numeric ID, not name. Look them up once with GET /api/3/fields and store them.
Start an automation for one contact POST /api/3/contactAutomations Only active automations accept contacts. Each API add counts as a fresh run, and the same contact can be added to one automation at most 100 times in 24 hours.
Create a deal or move it to another stage POST /api/3/deals, then PUT /api/3/deals/{id} Deals need the Pipelines feature on your plan. Stage and pipeline are IDs too.
Get told when something changes in ActiveCampaign POST /api/3/webhooks Pick the events (subscribe, unsubscribe, deal_update and more) and the sources: a contact, any user, the system, or the API.

ActiveCampaign webhook habits that surprise people

The webhook docs are short. These are the lines that matter most.

A missed delivery is gone

How you'll know: Your server was down for twenty minutes and those contacts never reached the other system.

Fix: ActiveCampaign says webhooks are never retried. Run a periodic catch-up that lists recent changes through the API and fills the gaps.

The same event arrives twice

How you'll know: Duplicate rows or double notes on the other side.

Fix: Delivery is at least once, so duplicates can happen. Make the receiver idempotent: check whether you've already handled that contact and change.

The webhook switched itself off

How you'll know: Events stopped entirely after a deploy.

Fix: Answering with a 410 deactivates the webhook for good. It has to be deleted and created again, so never return 410 from a route that's only briefly missing.

An import didn't fire anything

How you'll know: A CSV of 3,000 new contacts went in and the subscribe webhook stayed silent.

Fix: Mass inserts like imports don't trigger the subscribe webhook. Sync imported contacts separately.

Automation emails don't show up as campaign events

How you'll know: Opens and clicks from your welcome series never reach your webhook.

Fix: Campaigns sent by autoresponders and automations don't fire campaign webhooks. Use a Webhook step inside the automation for those.

Five integrations share five requests a second

How you'll know: 429s that appear only when the store sync and the CRM sync run together.

Fix: The limit is per account, not per key. Queue writes and honor Retry-After.

Account webhook or a Webhook step in an automation?

Account-level webhook

Fires on every matching event

  • Created through the API, for events like subscribes, unsubscribes, contact updates and deal changes.
  • Best when another system needs a full record of what changes, regardless of which automation caused it.
Automation Webhook action

Fires where you put it

  • A step in an automation that posts contact or deal data to your URL when a contact reaches it.
  • Best when the call should happen only after the automation's own conditions: a tag applied, a form submitted, a deal moved, a wait finished.

Many builds use both: API calls in, an automation step out for the moments marketing decides, and an account webhook as the full change log.

Copying an automation across accounts

There's no API to create or edit an automation's logic. Triggers, branches and actions live in the builder. ActiveCampaign's Share link copies an automation into another account, but only as it stood when shared. Every later change means a new link, a new import and a manual check in each account. That hurts when an agency runs the same nurture in a dozen client accounts.

For that job, n-frames uses browser automation to apply the change in each account, then checks the result, so a change that took an afternoon per account takes minutes. Everything else, contacts, deals, fields and starting a contact in an automation, goes through the API. The deal-to-invoice flow on the main ActiveCampaign page and the pipeline work on the ActiveCampaign CRM page both run on it.

Questions people ask

Where do I find my ActiveCampaign API URL and key?

Open Settings and choose Developer. Your account's API URL and your own API key are both on that page, and every request needs both: the URL as the base, the key in the Api-Token header.

Can I create or edit an ActiveCampaign automation through the API?

No. The API can add a contact to an existing, active automation and manage contacts, deals and tags, but the automation's triggers and steps are built in the builder by a person. A share link copies one across accounts as a one-time snapshot; keeping a dozen copies in step is the part n-frames automates.

Does ActiveCampaign support webhooks?

Yes, in two forms. Account-level webhooks, created through the API, fire on events like subscribes, contact updates and deal changes. Inside an automation, a Webhook action posts contact or deal data to your URL when a contact reaches that step.

Is the ActiveCampaign API included with every plan?

The API itself isn't split by plan in ActiveCampaign's developer docs, and the published limit, 5 requests per second, applies per account. What you can reach does depend on the plan: deals, for example, need the Pipelines feature. Confirm the features a high-volume integration needs before you build it.

What is the ActiveCampaign Deals API used for?

Creating deals, updating them and moving them between pipeline stages from code. It's what lets a stage change follow a real event, like a signed contract or a cleared credit check in another system, instead of a rep's guess.

Why am I getting 429 errors from ActiveCampaign?

You've passed 5 requests per second on the account. Every integration on that account shares the budget. Wait the number of seconds in the Retry-After header, and queue writes so bursts don't stack up.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.