Install Jentic One Beta

Connect the Daktela API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Daktela 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdaktela.com%2Fdaktela" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdaktela.com%2Fdaktela" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Daktela API.

Authenticate with username and password to obtain a Daktela access token via POST /login.json

List all customer activities across channels with GET /activities.json

Retrieve only call activities for telephony reporting via GET /activitiesCall.json

Pull email activities for omnichannel agent productivity reviews

Read SMS, Facebook Messenger, Instagram DM, and Viber activities for social channel reporting

GET STARTED

Start building with Daktela API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Daktela API for, with concrete tasks.

★ Omnichannel Reporting Pipeline

BI teams that need a unified view of contact-centre activity pull from /activities.json or per-channel endpoints into a data warehouse on a schedule. Because Daktela's ACL engine ties each token to a user, the agent uses a service account with read access to all channels and writes the response payloads into a flat fact table for downstream dashboarding.

Authenticate with POST /login.json, then GET /activities.json filtered to the last 24 hours and write the response into a 'fact_activity' table.

Per-Channel Volume Tracking

Operations managers tracking volume on each channel separately (calls, emails, SMS, Facebook DMs) call the channel-specific endpoints (/activitiesCall.json, /activitiesEmail.json, /activitiesSms.json, /activitiesFbm.json, /activitiesIgdm.json, /activitiesVbr.json) on a daily cadence. Hitting per-channel endpoints rather than the unified one is faster when only one or two channels are in scope.

Call GET /activitiesCall.json for the previous shift window, count rows, and post the value to a Slack channel.

CRM-to-Daktela Activity Sync

When a CRM (HubSpot, Salesforce) needs a record of every customer interaction handled in Daktela, an integration agent authenticates against /login.json, pulls /activities.json for each contact, and writes the activity records back to the CRM as engagement entries. This gives sales and success teams a single timeline that includes contact-centre conversations.

For each CRM contact, GET /activities.json filtered by phone number and POST a matching engagement record into HubSpot.

Agent-Assisted QA Sampling

An AI agent supporting a contact-centre QA team samples recent call and email activities to surface candidate interactions for review. The agent calls /activitiesCall.json and /activitiesEmail.json, applies internal scoring rules, and produces a shortlist for the QA reviewer instead of having someone scroll through the Daktela UI.

Sample 50 random rows from /activitiesCall.json over the past week and produce a CSV with caller, duration, and agent.

Key Endpoints

8 endpoints — daktela is a contact-centre and omnichannel communications platform widely used in central and eastern europe.

METHOD

PATH

DESCRIPTION

POST

/login.json

GET

/activities.json

List unified customer activities

GET

/activitiesCall.json

List call activities

GET

/activitiesEmail.json

List email activities

GET

/activitiesSms.json

List SMS activities

GET

/activitiesFbm.json

List Facebook Messenger activities

GET

/activitiesIgdm.json

List Instagram DM activities

GET

/activitiesVbr.json

List Viber activities

POST

/login.json

GET

/activities.json

List unified customer activities

GET

/activitiesCall.json

List call activities

GET

/activitiesEmail.json

List email activities

GET

/activitiesSms.json

List SMS activities

GET

/activitiesFbm.json

List Facebook Messenger activities

GET

/activitiesIgdm.json

List Instagram DM activities

GET

/activitiesVbr.json

List Viber activities

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Daktela by hand means learning its X-AUTH-TOKEN header auth, resolving the per-instance {instance}.daktela.com/api/v6 host, and building the paging plumbing across each activity channel yourself. Through Jentic you install once, import the Daktela API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Daktela activity endpoints select records by request parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as logging in and listing call or email activities. Every operation the agent can run is one you added to that allowed set.

Credential isolation

Your Daktela X-AUTH-TOKEN and the per-instance hostname 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.

Intent-based discovery

Agents search Jentic by intent such as 'list Daktela call activities' or 'log in to Daktela', and Jentic returns the matching v6 operation with its input schema so the agent calls the right endpoint without browsing the customer.daktela.com docs.

FAQs

Specific to using Daktela API through Jentic.

What authentication does the Daktela API use?

Daktela's v6 API supports two API key schemes: X-AUTH-TOKEN in the request header and accessToken as a query parameter. You first call POST /login.json with username and password to obtain a token, then pass it on subsequent calls. Through Jentic the token is held in the encrypted vault and surfaced as a scoped runtime credential.

Can I list call activities through the Daktela API?

Yes. GET /activitiesCall.json returns call records for the authenticated user according to the Daktela ACL engine. For a unified feed across every channel, use GET /activities.json instead; for SMS, email, or social channels, the per-channel endpoints (/activitiesSms.json, /activitiesEmail.json, /activitiesFbm.json, /activitiesIgdm.json, /activitiesVbr.json) are more efficient.

What are the rate limits for the Daktela API?

The OpenAPI spec does not declare hard rate limits. Daktela's published guidance is that limits are enforced per instance and per user; for steady reporting workloads, treat 5-10 requests per second per token as a safe ceiling and stagger long backfills.

How do I authenticate against a Daktela instance through Jentic?

Install pip install jentic and run an agent with the search query 'log in to Daktela'. Jentic returns the POST /login.json operation with its input schema; the agent supplies the instance hostname, username, and password, then receives the access token to use on subsequent activity calls.

Can I export activities to a data warehouse?

Yes. The /activities.json and per-channel endpoints return JSON payloads suitable for direct ingestion into a warehouse loader. Pace the calls to respect the per-instance limit and use date filters on each request to keep payload sizes manageable.

Does the Daktela API support sending outbound communications?

The 8 endpoints in this spec are scoped to authentication and activity listing. Outbound dial, outbound email, and outbound SMS are handled through the broader Daktela platform UI and other endpoints not exposed in this v6 subset; this REST surface is read-oriented.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Daktela operations the agent may call and which stored token it may use. Since the Daktela activity endpoints select records by request parameters rather than a resource id in the path, you scope access by adding only the operations the agent needs, such as POST /login.json plus GET /activitiesCall.json or GET /activitiesEmail.json, and leaving the rest out. Every operation the agent can run is one you added to that allowed set.

Daktela API

Name: Daktela API
Brand: Daktela API
Availability: InStock

Official vendor OpenAPI document · agent-readyCommunicationsVoice TelephonyapiKey8 EndpointsREST

For Agents

List call, email, SMS, and social messaging activities across a Daktela contact centre and authenticate to obtain access tokens for downstream calls.

Use for: I need to log in and get a Daktela access token, List all call activities from the last 24 hours, Retrieve email activities for a specific contact-centre user, Get SMS activities for the last week

Not supported: Does not handle outbound dial, outbound messaging, or contact-centre configuration - use for Daktela login and listing customer activities across channels only.

Daktela is a contact-centre and omnichannel communications platform widely used in central and eastern Europe. The v6 REST API exposes endpoints for authentication and for listing customer activity across call, email, SMS, Facebook Messenger, Instagram DM, and Viber channels. Every operation runs through Daktela's built-in ACL engine, meaning each call requires an access token tied to a specific user and instance. The API is positioned as the integration surface for connecting CRM systems, BI tools, and AI agents to a Daktela contact centre.

Jentic One on Github View OpenAPI Document