canonical: https://jentic.com/apis/reply.io/reply

# Reply.io API

Reply.io sales engagement API for managing campaigns, contacts, and email sequences. The API exposes 10 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create contact, list contacts. Covers 10 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Delete contact

## Use cases

### CRM Operations

Use the Reply.io API to perform crm operations programmatically. The API provides 10 endpoints covering core functionality including create contact, list contacts, get contact.

Example prompt: Call POST /contacts to create contact

### Automated Campaigns Management

Automate campaigns operations by combining multiple Reply.io API endpoints. Agents can list contacts and then get contact in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Reply.io 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contacts` | Create contact |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{id}` | Get contact |
| PUT | `/contacts/{id}` | Update contact |
| DELETE | `/contacts/{id}` | Delete contact |
| GET | `/campaigns` | List campaigns |
| GET | `/campaigns/{id}` | Get campaign |
| GET | `/sequences` | List sequences |

## Key resources

- **Campaigns** — Operations related to Campaigns
- **Contacts** — Operations related to Contacts
- **Email Accounts** — Operations related to Email Accounts
- **Sequences** — Operations related to Sequences
- **Stats** — Operations related to Stats

## Why Jentic

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

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Reply.io API use?

The Reply.io API uses an API key passed in the `X-Api-Key` 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 contact with the Reply.io API?

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

### What are the rate limits for the Reply.io 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 contact through Jentic?

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

### How many endpoints does the Reply.io API have?

The Reply.io API exposes 10 endpoints covering campaigns, contacts, email accounts operations.

### Can I limit what my agent is allowed to do with the Reply.io API?

Yes. Because you run Jentic One yourself, you decide which Reply.io operations and credentials your agent may use. Since Reply.io puts the contact id in the URL path (`/contacts/{id}`), you can pin the agent to reading or updating a specific contact rather than acting across your whole account. You also choose the operation set, so a destructive call like DELETE `/contacts/{id}` stays out of reach unless you explicitly grant it.