Etrigue API

Name: Etrigue API
Brand: Etrigue API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey10 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Etrigue API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Etrigue API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Etrigue API.

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

GET STARTED

Start building with Etrigue API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Etrigue API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault, so the agent operates on a scoped execution token.

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

10 endpoints — jentic publishes the only available openapi specification for etrigue api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Etrigue X-API-Key is stored encrypted in the Jentic vault. Agents call operations with a scoped execution token, so the raw API key never enters the agent's prompt or logs.

Intent-based discovery

Agents search Jentic with intents such as 'create a B2B lead' or 'log a marketing activity' and Jentic resolves them to the matching Etrigue operation along with its input schema.

Time to first call

Direct integration: 1 day to wire up the X-API-Key, lead/campaign/activity CRUD, and pagination. Through Jentic: under an hour for the first /leads call.

FAQs

Specific to using Etrigue API through Jentic.

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 at https://app.jentic.com/sign-up.

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'.

Etrigue API

Connect the Etrigue API to your agent

Capabilities

Start building with Etrigue API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs