v1.0.0 to v1.0.0

23 added, 0 removed. Audit A to A.

---

name: activecampaign

description: |

ActiveCampaign integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign. Routes through Apideck with serviceId "activecampaign".

license: Apache-2.0

alwaysApply: false

metadata:

author: apideck

version: "1.0.0"

serviceId: activecampaign

unifiedApis: ["crm"]

authType: apiKey

tier: "1c"

verified: true

+ difficulty: moderate

+ partnershipRequired: false

+ sandboxAvailable: true

---

# ActiveCampaign (via Apideck)

Access ActiveCampaign through Apideck's **CRM** unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, HubSpot and 17 other CRM connectors by changing a single `serviceId` string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant ActiveCampaign plumbing.

## Quick facts

- **Apideck serviceId:** `activecampaign`

- **Unified API:** CRM

- **Auth type:** apiKey

- **Gotchas:** [page](https://developers.apideck.com/apis/crm/activecampaign/gotchas)

- **ActiveCampaign docs:** https://developers.activecampaign.com

- **Homepage:** https://www.activecampaign.com/

+ ## At a glance

+ - **Implementation difficulty:** moderate — API Key Authentication - Each Consumer Copies Their Own Key from ActiveCampaign

+ - **Vendor partnership required:** no

+ - **Apideck-managed credentials:** not available — Each consumer supplies their own ActiveCampaign API URL and key.

+ - **Account type required:** An ActiveCampaign account.

+ - **Consumer access level:** A user who can open Settings > Developer; their key must be able to list users.

+ - **Sandbox:** available ([signup](https://developers.activecampaign.com/page/developer-sandbox-accounts)) — A free developer sandbox on request (1,000 contacts, 5 users; expires after two years, renewable by email), or a 14-day free trial that includes opportunities.

+ - **Costs:** Opportunities and pipelines need the Pipelines or Sales Engagement Enhanced CRM add-on, sold on the Plus, Professional and Enterprise plans, not on Starter.

+ - **Rate limits:** 5 requests a second for each account, shared by every integration and user on it.

+ - **Authentication:** Sent in the Api-Token header; not OAuth.

+ - **Webhooks:** No webhooks - neither native nor virtual; poll for changes.

+ **Important to know:**

+ - An API key belongs to the ActiveCampaign user who copied it, and there is no account default key. Deleting that user, or resetting their key, breaks the connection until another user's URL and key are pasted into Vault.

+ - ActiveCampaign has a single contact record: leads in the Lead API and contacts in the CRM API are the same people, so a change made through one appears in the other. Vault keys a connection to one unified API, so using both means two connections with the same URL and key.

+ > Facts synced from Apideck's connector metadata API — `GET /connector/connectors/activecampaign` (`overview` field) is the live, authoritative version.

## When to use this skill

Activate this skill when the user explicitly wants to work with **ActiveCampaign** — for example, "pull contacts in ActiveCampaign" or "sync leads in ActiveCampaign". This skill teaches the agent:

1. Which Apideck unified API covers ActiveCampaign (CRM)

2. The correct `serviceId` to pass on every call (`activecampaign`)

3. ActiveCampaign-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

- [`apideck-node`](../../skills/apideck-node/), [`apideck-python`](../../skills/apideck-python/), [`apideck-dotnet`](../../skills/apideck-dotnet/), [`apideck-java`](../../skills/apideck-java/), [`apideck-go`](../../skills/apideck-go/), [`apideck-php`](../../skills/apideck-php/), or [`apideck-rest`](../../skills/apideck-rest/)

For the raw OpenAPI spec:

- **CRM:** [https://specs.apideck.com/crm.yml](https://specs.apideck.com/crm.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=crm)

## Minimal example (TypeScript)

```typescript

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({

apiKey: process.env.APIDECK_API_KEY,

appId: process.env.APIDECK_APP_ID,

consumerId: "your-consumer-id",

});

// List contacts in ActiveCampaign

const { data } = await apideck.crm.contacts.list({

serviceId: "activecampaign",

});

```

## Portable across 21 CRM connectors

The Apideck **CRM** unified API exposes the same methods for every connector in its catalog. Switching from ActiveCampaign to another CRM connector is a one-string change — no rewrite, no new SDK.

```typescript

// Today — ActiveCampaign

await apideck.crm.contacts.list({ serviceId: "activecampaign" });

// Tomorrow — same code, different connector

await apideck.crm.contacts.list({ serviceId: "odoo" });

await apideck.crm.contacts.list({ serviceId: "salesforce" });

```

This is the compounding advantage of using Apideck over integrating ActiveCampaign directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

## Authentication

- **Type:** API Key

- **Managed by:** Apideck Vault — the user pastes their ActiveCampaign API key into the Vault modal; Apideck stores it encrypted and injects it on every request.

- **Rotation:** if the user rotates their key, they re-enter it in Vault. No code changes needed.

See [`apideck-best-practices`](../../skills/apideck-best-practices/) for Vault setup, connection lifecycle, and handling re-auth flows.

## Verifying coverage

Not every CRM operation is supported by every connector. Always verify before assuming a method works:

```bash

curl 'https://unify.apideck.com/connector/connectors/activecampaign' \

-H "Authorization: Bearer ${APIDECK_API_KEY}" \

-H "x-apideck-app-id: ${APIDECK_APP_ID}"

```

See [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) for patterns around `UnsupportedOperationError` and connector-specific fallbacks.

## Escape hatch: Proxy API

When an endpoint isn't covered by the CRM unified API, use Apideck's Proxy to call ActiveCampaign directly — Apideck injects auth headers and handles token refresh. Set `x-apideck-downstream-url` to the target endpoint on ActiveCampaign's own API:

```bash

curl 'https://unify.apideck.com/proxy' \

-H "Authorization: Bearer ${APIDECK_API_KEY}" \

-H "x-apideck-app-id: ${APIDECK_APP_ID}" \

-H "x-apideck-consumer-id: ${CONSUMER_ID}" \

-H "x-apideck-service-id: activecampaign" \

-H "x-apideck-downstream-url: <target endpoint on ActiveCampaign>" \

-H "x-apideck-downstream-method: GET"

```

See [ActiveCampaign's API docs](https://developers.activecampaign.com) for available endpoints.

## Sibling connectors

Other **CRM** connectors that share this unified API surface (same method signatures, just change `serviceId`):

[`odoo`](../odoo/) *(beta)*, [`salesforce`](../salesforce/), [`hubspot`](../hubspot/), [`pipedrive`](../pipedrive/), [`zoho-crm`](../zoho-crm/), [`close`](../close/), [`microsoft-dynamics`](../microsoft-dynamics/), [`teamleader`](../teamleader/), and 12 more.

## See also

- [CRM OpenAPI spec](https://specs.apideck.com/crm.yml) · [API Explorer](https://developers.apideck.com/api-explorer?id=crm)

- [`apideck-connector-coverage`](../../skills/apideck-connector-coverage/) — programmatic coverage checks

- [`apideck-best-practices`](../../skills/apideck-best-practices/) — architecture, Vault, pagination, error handling

- [`apideck-node`](../../skills/apideck-node/) — TypeScript / Node SDK patterns

- [ActiveCampaign official docs](https://developers.activecampaign.com)