Audienceful API

Name: Audienceful API
Brand: Audienceful API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey6 EndpointsREST

For Agents

Manage Audienceful subscribers and custom fields via a single X-Api-Key header so creator tools can sync new sign-ups into an email list.

Install Jentic One Beta

Connect the Audienceful API to your agent

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

Add a new subscriber to the list with POST /people/

Update a subscriber's email or custom fields via PATCH /people/

Remove a subscriber from the list via DELETE /people/

Page through every subscriber with GET /people/ for export or sync

GET STARTED

Start building with Audienceful API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Audienceful API, keeping it validated and agent-ready. Audienceful is a lightweight email marketing platform aimed at writers, creators, and small product teams. The REST API focuses on the two primitives a creator workflow needs: people (subscribers) and custom fields. With six endpoints it can create, update, list, and delete subscribers, and define the custom fields used to segment them. Authentication is a single X-Api-Key header so a writing tool or no-code automation can plug in quickly.

Use Cases

Patterns agents use Audienceful API for, with concrete tasks.

★ No-code form to newsletter sync

Creators capture sign-ups on a landing page or a Tally/Typeform form and want them in Audienceful without running a backend. POST /people/ accepts the email and any custom field values and creates the subscriber in one call. With a single X-Api-Key header the integration fits into Zapier, Make, or a serverless function in minutes.

Given a sign-up event with email and source fields, POST /people/ with the email and a custom field 'source' set to the form name.

Segment audiences with custom fields

A creator running both free and paid newsletters needs to segment subscribers by plan, interest, or source. POST /people/fields/ creates a custom field once, and PATCH /people/ updates each subscriber's value when their state changes (for example, after a Stripe payment webhook). GET /people/ paginates the audience for any later export or audit.

Create a custom field 'plan' via POST /people/fields/, then for each existing paid subscriber call PATCH /people/ with plan='premium'.

Bulk export and audit

When a creator needs an audit of their list before migrating tools or running a paid campaign, GET /people/ paginates the entire subscriber roster with all custom field values. The export can be loaded into a spreadsheet or pushed into a data warehouse for analysis without leaving the API.

Page GET /people/ until exhausted and write each subscriber's email and custom_fields to a CSV file.

AI agent integration via Jentic

A creator-assistant agent using Jentic can sync new readers into Audienceful without storing the X-Api-Key in the agent context. The agent searches an intent like 'add a subscriber to my newsletter', Jentic returns the matching POST /people/ operation with its input schema, and the call is executed with the apikey resolved from the Jentic vault.

Use Jentic search 'add a subscriber to Audienceful', load the schema for POST /people/, and execute it with email='reader@example.com' and a tag of 'beta-launch'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/people/

List subscribers

POST

/people/

Create a new subscriber

PATCH

/people/

Update a subscriber

DELETE

/people/

Delete a subscriber

GET

/people/fields/

List custom fields

POST

/people/fields/

Create a custom field

GET

/people/

List subscribers

POST

/people/

Create a new subscriber

PATCH

/people/

Update a subscriber

DELETE

/people/

Delete a subscriber

GET

/people/fields/

List custom fields

POST

/people/fields/

Why Jentic?

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

Credential isolation

Audienceful X-Api-Key values are stored encrypted in the Jentic vault. Agents receive scoped execution access; the raw key is never exposed to the agent's prompt or memory.

Intent-based discovery

Agents search by intent (e.g., 'add a subscriber to Audienceful') and Jentic returns the matching operation with its input schema, so the agent calls POST /people/ or POST /people/fields/ without browsing the help docs.

Time to first call

Direct Audienceful integration: a few hours to wire X-Api-Key handling and pagination. Through Jentic: under 15 minutes from search to first executed call.

FAQs

Specific to using Audienceful API through Jentic.

Why is there no official OpenAPI spec for Audienceful API?

Audienceful publishes prose API help at audienceful.com/help but does not distribute an OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call Audienceful 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 Audienceful API use?

The Audienceful API uses an API key passed in the X-Api-Key header on every request. The key is generated in the Audienceful account settings. Through Jentic the X-Api-Key is held in the vault and injected at execution time, so the raw key never reaches the agent's context.

Can I add a subscriber and set custom field values in one call with the Audienceful API?

Yes. POST /people/ accepts the email plus a custom_fields object in the request body, so a sign-up event can create the subscriber and tag them in a single round trip. PATCH /people/ updates fields on an existing subscriber.

What are the rate limits for the Audienceful API?

Audienceful does not declare rate limits in the spec. The service is aimed at creator-scale lists, so production integrations should pace bulk imports and watch for 429 responses on the /people/ endpoints rather than push thousands of writes per minute.

How do I sync new sign-ups into Audienceful through Jentic?

Run jentic search 'add a subscriber to Audienceful', load the schema for POST /people/, and execute it with the email and any custom field values. Jentic resolves the X-Api-Key from the vault at execution time. With pip install jentic the integration is one async call.

Is the Audienceful API available on every plan?

API access is part of Audienceful's paid tiers. The free trial is enough to validate an integration, and once an account is on a paid plan the same X-Api-Key continues to work without scope changes.

Audienceful API

Connect the Audienceful API to your agent

Capabilities

Start building with Audienceful API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs