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

# respond.io API

The respond.io Developer API enables developers to seamlessly integrate messaging capabilities into their existing platforms or applications. The API provides functionalities such as sending and receiving messages, managing contacts, and automating messaging campaigns. The API follows RESTful conventions and uses common methods like GET, POST, PUT, and DELETE. Request and response bodies are encod. The API exposes 28 endpoints secured with bearer authentication.

## For AI agents

Programmatically create or update a contact, list the contacts. Covers 28 operations with bearer authentication.

## Scope

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

## Capabilities

- Create or update a contact
- List the contacts
- Merge two contacts
- Get a contact
- Update a contact
- Delete a contact

## Use cases

### Communications Operations

Use the respond.io API to perform communications operations programmatically. The API provides 28 endpoints covering core functionality including create or update a contact, list the contacts, merge two contacts.

Example prompt: Call POST `/contact/create_or_update/{identifier}` to create or update a contact

### Automated Contact Management

Automate contact operations by combining multiple respond.io API endpoints. Agents can list the contacts and then merge two contacts in a single workflow.

Example prompt: Call POST `/contact/list` to list the contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call respond.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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contact/create_or_update/{identifier}` | Create or update a contact |
| POST | `/contact/list` | List the contacts |
| POST | `/contact/merge` | Merge two contacts |
| POST | `/contact/{identifier}` | Create a contact |
| GET | `/contact/{identifier}` | Get a contact |
| PUT | `/contact/{identifier}` | Update a contact |
| DELETE | `/contact/{identifier}` | Delete a contact |
| GET | `/contact/{identifier}/channels` | List contact channels |

## Key resources

- **Contact** — Manage contacts - access, create, update, or remove contacts in your workspace.
- **Messaging** — Send and retrieve messages for contacts.
- **Conversation** — Open and close conversations, assign and unassign contacts.
- **Comment** — Create comments on contacts for internal reference.
- **Space** — Manage workspace settings including users, channels, tags, custom fields, and closing notes.

## Why Jentic

- **Setup:** Wiring respond.io API by hand means learning its bearer token auth, pointing at the api.respond.io/v2 host, and handling contact and message flows yourself. Through Jentic you install once, import respond.io API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** respond.io API puts the contact identifier in the URL path (`/contact/{identifier}/...`), so a rule can pin your agent to one contact: it can read and update that contact and nothing else. You choose the operations it may call, so destructive ones like contact deletion or contact merge are not included unless you add them.
- **Credential handling:** Your respond.io 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.
- **Discovery method:** Agents search Jentic by intent such as 'create or update a contact' or 'read a contact's channels', and Jentic returns the matching respond.io API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

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

The respond.io 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 or update a contact with the respond.io API?

Yes. Use the POST `/contact/create_or_update/{identifier}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the respond.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 or update a contact through Jentic?

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

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

The respond.io API exposes 28 endpoints covering contact, messaging, conversation operations.

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

Yes. Because you self-host Jentic One, your own rules decide which respond.io API operations and credentials the agent may use. Since the API puts the contact identifier in the URL path, such as `/contact/{identifier}`, you can pin the agent to a single contact and let it only read and update that record. You also choose the exact operations it may call, so destructive ones like DELETE `/contact/{identifier}` or POST `/contact/merge` stay off unless you add them.