Relatel Dk Relatel API
✓ Official Vendor SpecCommunicationsVoice Telephonybearer43 EndpointsREST
For Agents
Programmatically list chat conversations, get chat by uuid. Covers 43 operations with bearer authentication.
Use for: I need to chat conversations, I want to chat by uuid, Search for recent orders, Find all order details
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
Relatel telephony platform API for managing chats, contacts, employees, receptions, voicemails, calls, messages, and statistics. The API exposes 43 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Relatel API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Relatel 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 Relatel API.
List chat conversations
Get chat by UUID
Create contact
Query and filter Relatel API records by parameters
Monitor Relatel API operational status and events
Use Cases
Patterns agents use Relatel API for, with concrete tasks.
★ Communications Operations
Use the Relatel API to perform communications operations programmatically. The API provides 43 endpoints covering core functionality including list chat conversations, get chat by uuid, list recent orders.
Call GET /chats to list chat conversations
Automated Calls Management
Automate calls operations by combining multiple Relatel API endpoints. Agents can get chat by uuid and then list recent orders in a single workflow.
Call GET /chats/{uuid} to get chat by uuid, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Relatel 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.
Search Jentic for 'list chat conversations', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
43 endpoints — relatel telephony platform api for managing chats, contacts, employees, receptions, voicemails, calls, messages, and statistics.
METHOD
PATH
DESCRIPTION
GET
/chats
List chat conversations
GET
/chats/{uuid}
Get chat by UUID
GET
/orders
List recent orders
GET
/orders/{id}
Get order details
POST
/contacts
Create contact
GET
/contacts
List contacts
GET
/contacts/{id}
Get contact
PUT
/contacts/{id}
Update contact
GET
/chats
List chat conversations
GET
/chats/{uuid}
Get chat by UUID
GET
/orders
List recent orders
GET
/orders/{id}
Get order details
POST
/contacts
Create contact
GET
/contacts
List contacts
GET
/contacts/{id}
Get contact
PUT
/contacts/{id}
Update contact
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Relatel API bearer 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., 'list chat conversations') and Jentic returns the matching Relatel API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Relatel 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 Relatel API through Jentic.
What authentication does the Relatel API use?
The Relatel API uses a Bearer token in the Authorization header. 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 list chat conversations with the Relatel API?
Yes. Use the GET /chats endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Relatel 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 list chat conversations through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list chat conversations'. Jentic returns the matching Relatel API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Relatel API have?
The Relatel API exposes 43 endpoints covering calls, chats, contacts operations.
GET STARTED