canonical: https://jentic.com/apis/etrigue.com/etrigue

# Etrigue API

Jentic publishes the only available OpenAPI specification for Etrigue API, keeping it validated and agent-ready. Etrigue is a B2B demand-generation and marketing-automation platform used by sales and marketing teams to manage leads, campaigns, and the activities that connect them. The REST API exposes the three resources teams interact with most - leads, campaigns, and activities - with list-and-create endpoints for each, plus a get-by-id endpoint for retrieval and lead updates. Authentication is a single X-API-Key header.

## For AI agents

Create and read B2B leads, campaigns, and marketing activities in Etrigue to drive demand-generation workflows.

## Scope

Does not handle email rendering, deliverability, or CRM opportunity management - use for B2B lead, campaign, and activity tracking only.

## Capabilities

- Create new B2B leads in Etrigue from inbound webform submissions or enrichment tools
- List leads and filter by campaign or activity for sales follow-up
- Update an existing lead with newer contact, company, or scoring data
- Create campaigns and retrieve campaign performance details
- Log marketing activities (email opens, downloads, page views) against a lead
- Page through lead, campaign, and activity collections for nightly exports

## Use cases

### Inbound web-to-lead capture for B2B marketing

Marketing pushes website form submissions into Etrigue by POSTing each payload to /leads with the prospect's email, company, and campaign context. The created lead is immediately available to sales, and a follow-up POST to /activities logs the originating form submission for attribution. This avoids a custom webhook receiver inside Etrigue.

Example prompt: POST /leads with the form fields, capture the returned leadId, then POST /activities with type 'form_submission' linked to that leadId and the originating campaignId.

### Campaign performance reporting in a BI tool

Analytics teams pull /campaigns and /activities nightly and load them into a BI warehouse alongside CRM and ads data. Each campaign's activity counts feed dashboards that compare cost-per-lead and engagement across channels. Because the API exposes paged list endpoints, the export is straightforward to schedule.

Example prompt: GET /campaigns, then for each campaignId GET /activities with that campaign filter and write the result to the BI warehouse table.

### Lead enrichment and scoring updates from an external tool

When an enrichment vendor or scoring model emits updated data for a known prospect, the workflow calls PUT `/leads/{leadId}` with the new fields so Etrigue reflects the latest contact, firmographic, and score values. Sales reps then see the freshest record without manual data entry.

Example prompt: For each lead in the enrichment queue, PUT `/leads/{leadId}` with the updated company, jobTitle, and score fields.

### AI agent triaging the marketing-qualified-lead queue

An AI agent assigned to triage MQLs lists fresh leads via /leads, fetches the recent activities for each via /activities, and assigns a priority based on whether the lead has interacted with high-intent campaigns. The Etrigue X-API-Key stays in your Jentic One instance, so the agent operates on a scoped execution token.

Example prompt: Search Jentic for 'list Etrigue leads', execute GET /leads, then for each lead GET /activities filtered by leadId and produce a priority list for the SDR team.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/leads` | List leads |
| POST | `/leads` | Create a lead |
| PUT | `/leads/{leadId}` | Update a lead by ID |
| GET | `/campaigns` | List campaigns |
| POST | `/campaigns` | Create a campaign |
| GET | `/activities` | List marketing activities |
| POST | `/activities` | Create a marketing activity |

## Key resources

- **Leads** — Create, list, retrieve, and update B2B leads
- **Campaigns** — Create, list, and retrieve marketing campaigns
- **Activities** — Create, list, and retrieve marketing activities tied to leads and campaigns

## Why Jentic

- **Setup:** Wiring the Etrigue API by hand means passing the X-API-Key header, targeting the /v1 base URL, and mapping lead, campaign, and activity payloads yourself. Through Jentic you install once, import the Etrigue API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Etrigue puts the lead id in the URL path (`/leads/{leadId}`), so a rule can pin your agent to updating one lead: it reads and updates that lead and nothing else. You choose the operations it may call, so a broader write like creating campaigns is not included unless you add it.
- **Credential handling:** Your Etrigue X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a B2B lead' or 'log a marketing activity', and Jentic returns the matching Etrigue operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **eSputnik API** — eSputnik covers consumer-focused omnichannel messaging where Etrigue focuses on B2B demand generation.
- **Pardot API** — Pardot is Salesforce's B2B marketing automation platform with leads, campaigns, and activities.
- **EspoCRM REST API** — EspoCRM holds the downstream sales CRM record that an Etrigue lead converts into.

## FAQ

### Why is there no official OpenAPI spec for Etrigue API?

Etrigue does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Etrigue API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Etrigue API use?

Etrigue uses an apiKey passed in the X-API-Key header. Through Jentic, that key is held encrypted in the vault and the agent only sees a scoped execution token, so the raw key never enters the agent's prompt context.

### Can I update an existing lead with the Etrigue API?

Yes - PUT `/leads/{leadId}` updates the lead with whatever fields you supply. Combine it with GET `/leads/{leadId}` first to read the current values if your workflow needs to merge changes rather than overwrite.

### What are the rate limits for the Etrigue API?

Etrigue does not publish a numeric rate-limit policy in this spec. Treat list endpoints as paginated, cache campaign and activity definitions client-side, and back off on any 429 or 5xx response.

### How do I capture an inbound lead through Jentic?

Search Jentic for 'create a B2B lead in Etrigue'. Jentic returns POST /leads with the field schema (email, firstName, lastName, company, campaignId). Execute it with the form payload and capture the returned leadId for follow-up activity logging.

### Are activities scoped to leads, campaigns, or both?

An activity can reference both a leadId and a campaignId; it is the join record that ties a piece of engagement to the lead who performed it and the campaign that drove it. List endpoints accept either filter so you can answer 'all activities for this lead' or 'all activities in this campaign'.

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

Yes. Because you run Jentic One yourself, your own rules decide which Etrigue operations and credentials the agent may use. Since Etrigue puts the lead id in the URL path (PUT `/leads/{leadId}`), you can pin the agent to reading and updating a single lead and nothing else. You choose the operations it may call, so a broader write such as POST /campaigns or POST /activities is excluded unless you explicitly add it.