Reteno API
✓ Official Vendor SpecCommunicationsEmail Deliverybasic71 EndpointsREST
For Agents
Programmatically add/update contact, delete contact by external id. Covers 71 operations with basic authentication.
Use for: I need to add/update contact, I want to contact by external id, Search for subscribe contact, Find all contacts
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
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.
Install Jentic One Beta
Connect the Reteno API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reteno 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Reteno API.
Add/update contact
Delete contact by external ID
Subscribe contact
Search contacts
Bulk add/update contacts
Get import status
Use Cases
Patterns agents use Reteno API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'add/update contact', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
71 endpoints — reteno omnichannel marketing platform api for managing contacts, events, messages (email, sms, push, inbox), segments, workflows, broadcasts, and analytics.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Reteno API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'add/update contact') and Jentic returns the matching Reteno API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Reteno API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Reteno API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED