canonical: https://jentic.com/apis/elite-funnels.com/elite-funnels # Elite Funnels Website API Jentic publishes the only available OpenAPI specification for Elite Funnels Website API, keeping it validated and agent-ready. The Website API is a small REST surface for sites built on the Elite Funnels platform, exposing 6 endpoints focused on contact management - list, create, search-by-email, retrieve, update, and delete. Calls authenticate with an HTTP bearer token against a tenant-specific base URL of the form https://{domain}/api/site, where {domain} is the published site's hostname. ## For AI agents Manage contacts on an Elite Funnels website: list, create, search by email, retrieve, update, and delete. Authenticated with a bearer token against the site's own domain. ## Scope Does not handle order processing, product catalogue management, webhooks, or page rendering - use for funnel-site contact CRUD only. ## Capabilities - Create new contact records via POST /contacts when a visitor submits a form - Look up an existing contact by email using GET `/contacts/search-by-email` - List all contacts on the site for export or audience segmentation - Update a contact's details after a checkout or profile change - Delete a contact to honour a data-removal request - Retrieve a single contact by ID for personalisation on a return visit ## Use cases ### Lead Capture from Funnel Pages Capture leads from Elite Funnels landing pages and sync them into a CRM or email tool by calling POST /contacts on form submission and GET `/contacts/search-by-email` to deduplicate. The 6-endpoint surface keeps the integration trivial for a serverless function or webhook handler. Suitable for funnels capturing thousands of leads per campaign. Example prompt: On form submission, search for the contact by email; if not found, create a new contact with name, email, and phone, then return the contact ID ### Contact List Export Export the full contact list from an Elite Funnels site for cleanup, migration, or external analytics. The list endpoint supports pagination, and individual contacts can be re-fetched by ID for full detail. Useful when re-platforming or building a data warehouse view of funnel leads. Example prompt: Page through GET /contacts until exhausted and write each contact record to a CSV for import into a CRM ### Privacy and Data-Subject Requests Honour data-subject requests by searching for the contact by email, retrieving the full record for export, and then issuing DELETE `/contacts/{id}` to remove the entry. The search-by-email endpoint avoids needing to scan the list, which keeps the workflow fast even on large sites. Example prompt: Search for the contact with email user@example.com, export their record to JSON, then call DELETE `/contacts/{id}` ### AI Agent Integration via Jentic Build an AI agent that takes a phone-call transcript, extracts the lead's name and email, deduplicates against the Elite Funnels contact list, and creates or updates the contact accordingly. Through Jentic, the agent searches by intent, loads the contact-creation schema, and executes without holding the bearer token in its prompt. Example prompt: Search Jentic for 'create a contact from a form submission', load the schema for POST /contacts, and create a contact extracted from a transcript ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/contacts` | List all contacts | | POST | `/contacts` | Create a new contact | | GET | `/contacts/search-by-email` | Search for a contact by email | | GET | `/contacts/{id}` | Retrieve a contact by ID | | PUT | `/contacts/{id}` | Update a contact | | DELETE | `/contacts/{id}` | Delete a contact | ## Key resources - **Contacts** — List, create, search-by-email, retrieve, update, and delete contact records on a site ## Why Jentic - **Setup:** Wiring the Elite Funnels Website API by hand means pointing at your own funnel domain, handling its bearer auth, and setting the Authorization header on every call yourself. Through Jentic you install once, import the Website API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** The Website API puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to one contact for reads and updates. You choose the operations it may call, so DELETE `/contacts/{id}` is not included unless you add it. - **Credential handling:** Your Elite Funnels bearer token 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 contact' or 'find a contact by email', and Jentic returns the matching Website API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **HubSpot CRM Contacts API** — HubSpot is a full CRM alternative when the funnel volume outgrows Elite Funnels' contact endpoints - **Mailchimp API** — Mailchimp can receive Elite Funnels contacts as audience members for email campaigns - **Pipedrive API** — Pipedrive turns funnel contacts into sales-pipeline deals ## FAQ ### Why is there no official OpenAPI spec for Elite Funnels Website API? Elite Funnels publishes its API reference as Apiary documentation rather than as a versioned OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call the Elite Funnels Website 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 Elite Funnels Website API use? The Website API uses HTTP bearer authentication. Through Jentic, the bearer token is stored encrypted in the vault and scoped per execution; the agent never sees the raw token in its prompt or logs. ### Can I look up a contact by email with this API? Yes. GET `/contacts/search-by-email` accepts an email query parameter and returns the matching contact, which is the recommended way to deduplicate before creating a new contact via POST /contacts. ### What is the base URL for the Elite Funnels Website API? The base URL is https://{domain}/api/site where {domain} is the published Elite Funnels site's own hostname. There is no shared platform endpoint - every site has its own. ### How do I create a contact through Jentic? Run the Jentic search query 'create a contact from a form submission', load the input schema for POST /contacts, then execute with the contact's name, email, and phone. The bearer token is injected by Jentic at execution time. ### How do I delete a contact for a GDPR request? First call GET `/contacts/search-by-email` to find the contact ID, then DELETE `/contacts/{id}.` There is no soft-delete endpoint, so the record is removed immediately. ### Can I limit what my agent is allowed to do with the Elite Funnels Website API? Yes. Because you run Jentic One yourself, your own rules decide which of the six contact operations the agent may call, so you can grant list, create, search-by-email, retrieve, and update while leaving DELETE `/contacts/{id}` out unless you explicitly add it. Since the contact id sits in the URL path (`/contacts/{id}`), you can also pin the agent to a single contact for reads and updates rather than the whole list. The bearer token is held by your instance and injected at execution time, so the agent never gets the raw credential.