canonical: https://jentic.com/apis/relatel.dk/relatel-dk

# Relatel Dk Relatel API

Relatel telephony platform API for managing chats, contacts, employees, receptions, voicemails, calls, messages, and statistics. The API exposes 43 endpoints secured with bearer authentication.

## For AI agents

Programmatically list chat conversations, get chat by uuid. Covers 43 operations with bearer authentication.

## Scope

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

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list chat conversations', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Calls** — Operations related to Calls
- **Chats** — Operations related to Chats
- **Contacts** — Operations related to Contacts
- **Employee Groups** — Operations related to Employee Groups
- **Employees** — Operations related to Employees

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 78 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/relatel.dk/relatel-dk/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Relatel by hand means handling its bearer token auth against app.relatel.dk and mapping its chats, orders, and contacts endpoints yourself. Through Jentic you install once, import Relatel from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Relatel puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to reading and updating one contact. You choose the operations it may call, so creating contacts is not included unless you add it.
- **Credential handling:** Your Relatel 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 'list chat conversations' or 'look up a contact', and Jentic returns the matching Relatel 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 Relatel API use?

The Relatel 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 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Relatel operations and credentials the agent may use. Because Relatel puts the contact id in the URL path (`/contacts/{id}`), you can pin the agent to reading and updating a single contact while excluding broader calls like GET /chats or listing all contacts. Creating contacts with POST /contacts stays off unless you explicitly add that operation to the agent's allowed set.