canonical: https://jentic.com/apis/replyify.com/replyify

# Replyify API

Replyify API for email automation, campaign management, and prospect engagement tracking. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically create campaign, list campaigns. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create campaign
- List campaigns
- Get campaign
- Update campaign
- Delete campaign

## Use cases

### Analytics Operations

Use the Replyify API to perform analytics operations programmatically. The API provides 12 endpoints covering core functionality including create campaign, list campaigns, get campaign.

Example prompt: Call POST /campaigns to create campaign

### Automated campaigns Management

Automate campaigns operations by combining multiple Replyify API endpoints. Agents can list campaigns and then get campaign in a single workflow.

Example prompt: Call GET /campaigns to list campaigns, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Replyify 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.

Example prompt: Search Jentic for 'create campaign', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/campaigns` | Create campaign |
| GET | `/campaigns` | List campaigns |
| GET | `/campaigns/{campaignId}` | Get campaign |
| PUT | `/campaigns/{campaignId}` | Update campaign |
| DELETE | `/campaigns/{campaignId}` | Delete campaign |
| POST | `/prospects` | Create prospect |
| GET | `/prospects` | List prospects |
| GET | `/prospects/{prospectId}` | Get prospect |

## Key resources

- **campaigns** — Email campaign management
- **prospects** — Prospect management
- **sequences** — Email sequence management
- **analytics** — Campaign analytics

## Why Jentic

- **Setup:** Wiring Replyify by hand means setting its bearer auth on every request against the /v1 host and tracking campaign and prospect ids across create, read, update, and delete calls yourself. Through Jentic you install once, import the Replyify API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Replyify puts the campaign id in the URL path (`/campaigns/{campaignId}`), so a rule can pin your agent to reading and updating a campaign and its prospects. You choose the operations it may call, so a destructive one like campaign deletion is not included unless you add it.
- **Credential handling:** Your Replyify 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a campaign' or 'list prospects', and Jentic returns the matching Replyify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Replyify API use?

The Replyify 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 campaign with the Replyify API?

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

### What are the rate limits for the Replyify 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 campaign through Jentic?

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

### How many endpoints does the Replyify API have?

The Replyify API exposes 12 endpoints covering campaigns, prospects, sequences operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Replyify operations and credentials the agent may use. Because Replyify carries the campaign id in the URL path (`/campaigns/{campaignId}`), you can pin the agent to reading and updating a specific campaign and its prospects while excluding everything else. You choose the operations it can call, so a destructive one like campaign deletion (DELETE `/campaigns/{campaignId}`) stays off the list unless you add it.