Boast API

Name: Boast API
Brand: Boast API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer14 EndpointsREST

For Agents

Enrol contacts into testimonial request sequences, retrieve submitted video and written responses, and subscribe to Boast webhooks to react to new testimonials.

Install Jentic One Beta

Connect the Boast API to your agent

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

Enrol a contact into a testimonial request sequence and trigger automated outreach

Retrieve submitted video and written testimonial responses for an account

Create and remove webhook subscriptions to react to new responses in real time

GET STARTED

Start building with Boast API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Boast API for, with concrete tasks.

★ Automated Testimonial Collection

Enrol newly converted customers into a Boast sequence so they automatically receive a request to record a video or written testimonial. The API accepts the contact and sequence identifiers and Boast handles the email cadence, reminders, and form delivery. Teams use this to convert post-purchase signals into social proof without manual outreach.

Create a sequence_enrollment for contact ID 4521 in sequence ID 88 to send the post-purchase testimonial request

Real-Time Response Pipeline

Subscribe to Boast webhook events to receive new testimonial responses the moment they are submitted, then route them into review, moderation, or publishing systems. The /accounts/{account_id}/webhook_subscriptions endpoints register and deregister these subscriptions. Useful for marketing teams who want to syndicate fresh testimonials to landing pages or CRM activity feeds.

POST a new webhook_subscription for account 17 pointing to https://example.com/webhooks/boast for response.created events

Testimonial Library Sync

Pull every submitted response for an account on a schedule and sync it into a content management system or testimonial gallery. The /accounts/{account_id}/responses endpoint returns the full archive so agents can incrementally update local mirrors. This keeps marketing sites and sales decks current without manual exports.

GET /accounts/17/responses and write each response payload to the testimonials table

AI Agent Testimonial Workflows

An AI agent uses Jentic to discover Boast operations by intent, then enrols contacts and registers webhooks without ever handling the bearer token directly. Search the catalogue with the natural-language query, load the operation schema, and execute the call through the Jentic SDK. Integration drops from days of OAuth and webhook plumbing to a single search-load-execute cycle.

Search Jentic for 'enrol a contact into a testimonial sequence', load the operation, and execute it for contact 4521

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/accounts

List accounts the token has access to

POST

/accounts/{account_id}/contacts

Create a contact within an account

GET

/accounts/{account_id}/responses

List all submitted testimonial responses

POST

/accounts/{account_id}/sequence_enrollments

Enrol a contact in a testimonial sequence

DELETE

/accounts/{account_id}/sequence_enrollments/{enrollment_id}

Remove a sequence enrolment

POST

/accounts/{account_id}/webhook_subscriptions

Subscribe to webhook events

DELETE

/accounts/{account_id}/webhook_subscriptions/{webhook_subscription_id}

Remove a webhook subscription

GET

/accounts

List accounts the token has access to

POST

/accounts/{account_id}/contacts

Create a contact within an account

GET

/accounts/{account_id}/responses

List all submitted testimonial responses

POST

/accounts/{account_id}/sequence_enrollments

Enrol a contact in a testimonial sequence

DELETE

/accounts/{account_id}/sequence_enrollments/{enrollment_id}

Remove a sequence enrolment

Why Jentic?

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

Credential isolation

Your Boast 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.

Intent-based discovery

Agents search Jentic by intent such as 'enroll a contact in a testimonial sequence' or 'list testimonial responses', and Jentic returns the matching Boast operation with its input schema so the agent calls the right endpoint without browsing the Boast docs.

Time to first call

FAQs

Specific to using Boast API through Jentic.

Why is there no official OpenAPI spec for Boast API?

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

Boast uses HTTP Bearer authentication. You obtain an OAuth 2.0 access token by posting to https://app.boast.io/oauth/token, then send it as Authorization: Bearer <token>. Through Jentic the token is stored in the encrypted vault and never reaches the agent context.

Can I enrol a contact into a testimonial sequence with the Boast API?

Yes. Send POST /accounts/{account_id}/sequence_enrollments with the contact_id and sequence_id in the body. Boast then runs the configured email cadence to request the testimonial.

How do I subscribe to new testimonial responses in real time?

Register a webhook with POST /accounts/{account_id}/webhook_subscriptions and supply your callback URL. Boast will POST to that URL when new responses are submitted. Remove the subscription with DELETE on the same path.

What are the rate limits for the Boast API?

Boast does not publish formal rate limits in this specification. Treat it as a low-volume marketing API and back off on HTTP 429 responses if encountered.

How do I list all testimonials for my account through Jentic?

Search Jentic for 'list testimonial responses', load the GET /accounts/{account_id}/responses operation, then execute it with your account_id. The Jentic SDK handles auth and pagination.

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

Yes. Because you run Jentic One yourself, your own rules decide which Boast operations and credentials the agent can use. Since Boast puts the account id in the URL path, such as /accounts/{account_id}/contacts and /accounts/{account_id}/responses, you can pin the agent to a single account so it only adds contacts and reads responses there. You also choose the exact operations it may call, so destructive actions like deleting a sequence enrollment or removing a webhook subscription stay off limits unless you add them.

Boast API

Connect the Boast API to your agent

Capabilities

Start building with Boast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs