Reachinbox API

Name: Reachinbox API
Brand: Reachinbox API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb Analyticsbearer66 EndpointsREST

For Agents

Programmatically create a new campaign, add sequences to a campaign. Covers 66 operations with bearer authentication.

Install Jentic One Beta

Connect the Reachinbox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reachinbox 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Freachinbox.ai%2Freachinbox" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freachinbox.ai%2Freachinbox" | 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 Reachinbox API.

Create a new campaign

Add sequences to a campaign

Set campaign schedule

Update campaign options and settings

GET STARTED

Start building with Reachinbox API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Reachinbox API for, with concrete tasks.

★ Analytics Operations

Use the Reachinbox API to perform analytics operations programmatically. The API provides 66 endpoints covering core functionality including create a new campaign, add sequences to a campaign, set campaign schedule.

Call POST /api/v1/campaigns/create to create a new campaign

Automated Campaigns Management

Automate campaigns operations by combining multiple Reachinbox API endpoints. Agents can add sequences to a campaign and then set campaign schedule in a single workflow.

Call POST /api/v1/campaigns/add-sequence to add sequences to a campaign, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Reachinbox API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'create a new campaign', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

66 endpoints — reachinbox.

METHOD

PATH

DESCRIPTION

POST

/api/v1/campaigns/create

Create a new campaign

POST

/api/v1/campaigns/add-sequence

Add sequences to a campaign

PUT

/api/v1/campaigns/set-schedule

Set campaign schedule

POST

/api/v1/campaigns/update-details

Update campaign options and settings

PUT

/api/v1/campaigns/set-accounts

Set sending accounts for a campaign

POST

/api/v1/campaigns/add-email

Add recipient emails to a campaign

POST

/api/v1/campaigns/remove-email

Remove an email from a campaign

POST

/api/v1/campaigns/start

Start a campaign

POST

/api/v1/campaigns/create

Create a new campaign

POST

/api/v1/campaigns/add-sequence

Add sequences to a campaign

PUT

/api/v1/campaigns/set-schedule

Set campaign schedule

POST

/api/v1/campaigns/update-details

Update campaign options and settings

PUT

/api/v1/campaigns/set-accounts

Set sending accounts for a campaign

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Reachinbox API by hand means setting up its bearer auth, sequencing the many campaign operations like create, add-sequence, set-schedule, and start, and passing campaign details in the request body yourself. Through Jentic you install once, import the Reachinbox API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Reachinbox API identifies campaigns through the request body rather than the URL path, so you limit the agent to the operations it needs, such as creating a campaign or adding a sequence. It only calls the operations you allow, so a step like starting a campaign is out of scope unless you add it.

Credential isolation

Your Reachinbox API 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 'create a new campaign' or 'set a campaign schedule', and Jentic returns the matching Reachinbox API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Reachinbox API through Jentic.

What authentication does the Reachinbox API use?

The Reachinbox API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a new campaign with the Reachinbox API?

Yes. Use the POST /api/v1/campaigns/create endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Reachinbox API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a new campaign through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new campaign'. Jentic returns the matching Reachinbox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Reachinbox API have?

The Reachinbox API exposes 66 endpoints covering campaigns, leads, leadlists operations.

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

Yes. Because you run Jentic One yourself as a self-hosted layer, your own rules decide which Reachinbox API operations and credentials the agent may use. The Reachinbox API identifies campaigns through the request body rather than the URL path, so you scope the agent to only the operations it needs, such as creating a campaign or adding a sequence. Any operation you do not allow, like starting a campaign or setting sending accounts, stays out of reach.

Reachinbox API

Connect the Reachinbox API to your agent

Capabilities

Start building with Reachinbox API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs