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

# Reteno API

Reteno omnichannel marketing platform API for managing contacts, events, messages (email, SMS, push, inbox), segments, workflows, broadcasts, and analytics. The API exposes 71 endpoints secured with basic authentication.

## For AI agents

Programmatically add/update contact, delete contact by external id. Covers 71 operations with basic authentication.

## Scope

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

## Capabilities

- Add/update contact
- Delete contact by external ID
- Subscribe contact
- Search contacts
- Bulk add/update contacts
- Get import status

## Use cases

### Communications Operations

Use the Reteno API to perform communications operations programmatically. The API provides 71 endpoints covering core functionality including add/update contact, delete contact by external id, subscribe contact.

Example prompt: Call POST /contacts to add/update contact

### Automated Account Management

Automate account operations by combining multiple Reteno API endpoints. Agents can delete contact by external id and then subscribe contact in a single workflow.

Example prompt: Call DELETE `/contacts/{externalCustomerId}` to delete contact by external id, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contacts` | Add/update contact |
| DELETE | `/contacts/{externalCustomerId}` | Delete contact by external ID |
| POST | `/contacts/subscribe` | Subscribe contact |
| GET | `/contacts/search` | Search contacts |
| POST | `/contacts/bulk` | Bulk add/update contacts |
| POST | `/contacts/bulk/file` | Bulk add from file |
| GET | `/contacts/import/status` | Get import status |
| GET | `/contacts/{id}/emails` | Get contact emails |

## Key resources

- **Account** — Operations for account
- **Auth** — Operations for auth
- **Broadcasts** — Operations for broadcasts
- **Catalogs** — Operations for catalogs
- **Contacts** — Operations for contacts

## Why Jentic

- **Setup:** Wiring the Reteno API by hand means setting up its basic auth, targeting the api.reteno.com/api host, and managing contact create, search, and bulk calls yourself. Through Jentic you install once, import Reteno API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Reteno API puts the customer id in the URL path (`/contacts/{externalCustomerId}`, `/contacts/{id}/emails`), so a rule can pin your agent to one contact: it can read that contact's emails and nothing else. You choose the operations it may call, so destructive ones like contact deletion are not included unless you add them.
- **Credential handling:** Your Reteno API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add or update a contact' or 'search contacts', and Jentic returns the matching Reteno 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 Reteno API use?

The Reteno API uses HTTP Basic authentication with username and password. 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 add/update contact with the Reteno 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 Reteno 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 add/update contact through Jentic?

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

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

The Reteno API exposes 71 endpoints covering account, auth, broadcasts operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Reteno API operations and credentials the agent may use. Because Reteno puts the customer id in the URL path (`/contacts/{externalCustomerId}`, `/contacts/{id}/emails`), a rule can pin the agent to a single contact so it can read that contact's emails and nothing more. You choose the exact operations it may call, so destructive ones like contact deletion via DELETE `/contacts/{externalCustomerId}` are excluded unless you add them.