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

# Axerto API

Jentic publishes the only available OpenAPI specification for Axerto API, keeping it validated and agent-ready. Axerto is a landing page and lead management platform that exposes a Zapier-style integration surface for retrieving landing pages, listing recent leads, and subscribing or unsubscribing webhooks for new lead events. The API uses an X-API-Key header for authentication and is designed for connecting Axerto landing pages to downstream automation and CRM tooling.

## For AI agents

Pull leads and landing pages out of Axerto and subscribe webhooks for new-lead events. Designed for marketing automations that route Axerto leads into CRM or messaging tools.

## Scope

Does not handle landing-page editing, A/B testing, or campaign creation - use for retrieving Axerto leads and landing-page metadata and managing lead webhooks only.

## Capabilities

- Verify an Axerto API key via the auth test endpoint before further calls
- List landing pages owned by the authenticated Axerto account
- Retrieve recently captured leads from Axerto landing pages
- Subscribe a webhook URL to receive notifications when new leads arrive
- Unsubscribe a previously registered webhook from Axerto lead events

## Use cases

### Lead Routing to CRM

Axerto users can pipe new leads from their landing pages into a CRM by subscribing a webhook to Axerto and forwarding the payload onward. The `/api/zapier/subscribe` endpoint registers a destination URL and `/api/zapier/leads` can backfill recent leads. Suited to small marketing teams that capture leads on Axerto and need them to land in HubSpot, Pipedrive, or similar.

Example prompt: POST `/api/zapier/subscribe` with the CRM webhook URL and pull the latest leads from GET `/api/zapier/leads` to backfill recent captures

### Landing Page Inventory

Marketing operators can list every Axerto landing page tied to their account via GET `/api/zapier/landings` - useful for building a campaign dashboard or auditing which pages are live. Pair with the leads endpoint to attribute captures to specific landing pages.

Example prompt: GET `/api/zapier/landings` and produce a table of landing-page ids and names for the connected Axerto account

### Real-Time Lead Notifications

Sales reps can be paged the moment an Axerto lead is captured by registering a webhook via `/api/zapier/subscribe` and routing the payload into Slack, SMS, or email. Cleanup is handled by `/api/zapier/unsubscribe` when the campaign ends. Ideal for time-sensitive lead follow-up workflows.

Example prompt: Register a Slack webhook via POST `/api/zapier/subscribe` so the sales channel is pinged the moment a new Axerto lead is captured

### Agent-Triggered Lead Sync via Jentic

A marketing agent can pull recent Axerto leads on a schedule and push them into other tools via Jentic without exposing the X-API-Key. Jentic isolates the credential and exposes the leads, landings, and webhook operations as discoverable tools. Suited to agents that orchestrate marketing-funnel data movement.

Example prompt: Search Jentic for 'list recent leads from axerto', load GET `/api/zapier/leads`, and execute the call to fetch leads since the last sync

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/zapier/auth` | Test authentication |
| GET | `/api/zapier/landings` | List landing pages |
| GET | `/api/zapier/leads` | List recent leads |
| POST | `/api/zapier/subscribe` | Subscribe a webhook |
| DELETE | `/api/zapier/unsubscribe` | Unsubscribe a webhook |

## Key resources

- **Auth** — Endpoint to verify the X-API-Key is valid before issuing other calls
- **Landings** — List of landing pages owned by the authenticated account
- **Leads** — Recently captured leads across the account's landing pages
- **Webhooks** — Subscribe and unsubscribe webhook URLs for new-lead notifications

## Why Jentic

- **Setup:** Wiring the Axerto API by hand means attaching an X-API-Key header on every call, polling for new leads, and standing up webhook subscribe and unsubscribe listeners yourself. Through Jentic you install once, import the Axerto API from the API Directory, store the X-API-Key once, and your agent calls it.
- **Permission scoping:** Axerto's operations are a small fixed set and its subscribe and unsubscribe calls carry their target in the request body rather than the URL, so scoping is by operation: limit the agent to the operations it needs, such as listing leads or landing pages. You choose which operations it may call, so unsubscribing a webhook is only available if you include it.
- **Credential handling:** Your Axerto X-API-Key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list recent leads' or 'subscribe a webhook to leads', and Jentic returns the matching Axerto operation with its input schema so the agent calls the right endpoint without wiring key handling code.

## Related APIs

- **Webflow API** — Webflow offers landing page and form-submission APIs as a competing site builder.
- **HubSpot API** — Common destination CRM that consumes Axerto leads via webhook routing.
- **Pipedrive API** — Sales CRM that pairs with Axerto for lead-to-deal handoff.

## FAQ

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

Axerto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Axerto 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 Axerto API use?

Axerto uses an API key passed in the X-API-Key header. Through Jentic, the key is stored encrypted and only injected at request time so the raw key never enters the agent context. Use GET `/api/zapier/auth` to verify the key is valid.

### Can I subscribe to new lead events with the Axerto API?

Yes. POST `/api/zapier/subscribe` registers a webhook URL that Axerto will call when a new lead is captured, and DELETE `/api/zapier/unsubscribe` removes the registration.

### How do I pull recent leads through Jentic?

Search Jentic for 'list recent leads from axerto', load the GET `/api/zapier/leads` schema, and execute it. Jentic injects the X-API-Key from the vault and returns the lead list to your agent.

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

The Axerto OpenAPI spec does not declare published rate limits. Treat the integration as a Zapier-style polling and webhook surface and back off on 429 responses if encountered.

### Is the Axerto API free to use?

API access is gated by your Axerto account plan. Pricing and inclusion of the API tier are controlled in your Axerto account, not in the API itself.

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

Yes. Because you run Jentic One yourself, your own rules decide which Axerto operations the agent may call, so you scope access by operation from the small fixed set: listing leads (GET `/api/zapier/leads`), listing landing pages (GET `/api/zapier/landings`), and subscribing or unsubscribing webhooks (POST `/api/zapier/subscribe`, DELETE `/api/zapier/unsubscribe`). If you grant only the read operations, the agent can pull leads and landing pages but cannot register or remove a webhook, since unsubscribe is available only when you include it. The X-API-Key you store is injected at request time under your control, so the agent acts within exactly the operations you allow.