Website API

Name: Website API API
Brand: Website API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer6 EndpointsREST

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

Connect the Website API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Website 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.

Install Jentic One Beta (Self-Hosted)

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

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 Website API API.

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

GET STARTED

Start building with Website API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Website API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Website API API for, with concrete tasks.

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

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.

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.

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.

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

6 endpoints — jentic publishes the only available openapi specification for elite funnels website api, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

The Elite Funnels bearer token is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents never see the raw token in prompts, memory, or logs.

Intent-based discovery

Agents search by intent (e.g. 'create a contact' or 'find contact by email') and Jentic returns the matching Website API operation with its input schema, so the agent picks the right endpoint without browsing Apiary docs.

Time to first call

Direct integration: 2-4 hours to handle the per-site base URL pattern and bearer auth. Through Jentic: under 10 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot CRM Contacts API

HubSpot is a full CRM alternative when the funnel volume outgrows Elite Funnels' contact endpoints

Choose HubSpot when contacts need rich pipelines, properties, and engagement history; choose Elite Funnels Website API for in-funnel contact capture only.

Complementary

Mailchimp API

Mailchimp can receive Elite Funnels contacts as audience members for email campaigns

Pair Mailchimp with Elite Funnels by syncing newly created contacts into a Mailchimp list for follow-up email sequences.

Complementary

Pipedrive API

Pipedrive turns funnel contacts into sales-pipeline deals

Use Pipedrive downstream of Elite Funnels when captured contacts need to enter a sales pipeline with stages and activities.

FAQs

Specific to using Website API API through Jentic.

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

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.