Embedery API

Name: Embedery API API
Brand: Embedery API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey4 EndpointsREST

For Agents

List, create, fetch, and delete on-site widgets and lead-capture forms hosted by Embedery so they can be provisioned by an agent.

Connect the Embedery API to your agent

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

List every embed configured in the workspace with its identifier and basic metadata

Create a new embed for a sign-up form, popup, or banner without using the dashboard

Retrieve a single embed by ID to inspect its configuration before mutating

Delete an embed when a campaign or page is retired

GET STARTED

Start building with Embedery API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Embedery API, keeping it validated and agent-ready. Embedery hosts on-site widgets and forms — newsletter sign-ups, exit-intent popups, lead-capture overlays — that are dropped into a website and configured remotely. The API exposes the embed catalogue so agents and integrations can list, create, retrieve, and delete embeds programmatically. Use it to provision lead-capture widgets without clicking through the dashboard.

Use Cases

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

★ Programmatic Widget Provisioning

Spin up new sign-up forms or popups as part of a campaign deployment instead of configuring each manually in Embedery's dashboard. The API accepts an embed configuration payload and returns the new embed ID, which the deployment pipeline can attach to the relevant landing page. Marketing engineering teams use this to keep widget definitions in version control and roll them out alongside site changes.

POST /embeds with the desired widget configuration and store the returned embed ID in the campaign manifest.

Embed Inventory Audit

Periodically list all embeds in the workspace to retire orphaned widgets and validate that every active landing page is still tied to a real embed. The list endpoint returns all embeds with their IDs so a job can compare them against the live site map. Operations teams run this to keep the embed footprint in sync with current campaigns.

Call GET /embeds, cross-reference IDs against the active campaign list, and log any embeds that no longer have a referencing page.

Retiring Old Widgets

When a campaign ends, remove its widget from the site by deleting the embed rather than leaving it disabled in the dashboard. The delete endpoint removes the embed by ID so it stops rendering immediately. This keeps the on-site experience clean and the dashboard inventory accurate.

Call DELETE /embeds/{id} for each embed flagged for retirement and confirm the response is successful before updating the campaign manifest.

Agent-Driven Embed Lifecycle

An agent driving a marketing operations workflow creates new Embedery widgets at campaign launch and deletes them at campaign end, keeping the embed footprint aligned with active programmes. Through Jentic the agent searches by intent, loads the schema, and executes lifecycle calls without bespoke client code. Time to integrate drops from a day of dashboard automation to under an hour.

Search Jentic for 'create a website lead capture widget', execute POST /embeds at launch and DELETE /embeds/{id} at end-of-campaign, and log both events to the campaign audit trail.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/embeds

List all embeds

POST

/embeds

Create a new embed

GET

/embeds/{id}

Get an embed by ID

DELETE

/embeds/{id}

Delete an embed

GET

/embeds

List all embeds

POST

/embeds

Create a new embed

GET

/embeds/{id}

Get an embed by ID

DELETE

/embeds/{id}

Delete an embed

Why though Jentic?

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

Credential isolation

The Embedery API key is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw key never enters the agent's context, and Jentic injects it into the Authorization header at execution time.

Intent-based discovery

Agents search by intent (e.g., 'create a website lead capture widget') and Jentic returns the matching Embedery operations with their input schemas, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Embedery integration: half a day for client code and key handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

MailerLite API

Send the captured leads into MailerLite as new subscribers

Use after Embedery captures a lead to push the new subscriber into a MailerLite list and trigger a welcome flow.

Complementary

Encharge API

Marketing automation platform that consumes captured leads

Pair with Embedery when leads need to enter a multi-step nurture sequence in Encharge.

Complementary

Brevo API

Email marketing platform for newsletters and broadcasts

Use Brevo when the captured leads should land in a contact list and receive recurring newsletter sends.

FAQs

Specific to using Embedery API API through Jentic.

Why is there no official OpenAPI spec for Embedery API?

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

The API uses an API key passed in the Authorization header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the raw value never enters an agent's context.

Can I create a popup with the Embedery API?

Yes. POST /embeds creates a new embed and returns its ID. The configuration payload describes the widget type and content, so popups, sign-up forms, and banners can all be provisioned through the same call.

How do I list every embed in my workspace through Jentic?

Search Jentic for 'list website embeds', load the schema for GET /embeds, and execute it. The response is the full embed catalogue, ready to feed into an audit job.

What are the rate limits for the Embedery API?

The OpenAPI spec does not declare quantitative rate limits; limits are enforced by Embedery at the account level. Treat HTTP 429 responses as authoritative and respect any Retry-After header in the response.

Can I delete an Embedery widget when a campaign ends?

Yes. DELETE /embeds/{id} removes the embed so it stops rendering. This is the correct pattern for retiring a campaign rather than disabling the widget in the dashboard.