api_filter

Dstny's APIs

Connect your own systems to telephony, call statistics, recordings and conversation data. See which API fits, who can use it and how you get access.

Choose the right API

Each API has its own credentials. A ticket or token for one API does not work on another.

API Use it for Who can use it Login How you get access
User API Call control, presence, contacts and queues for a single user All customers Ticket (Bearer) You create a ticket at bc.dstny.se
Analytics API Call statistics and call details for your own reports or data warehouse Customers with Dstny Analytics JWT or signed request You create an API ticket in reports.dstny.se
Call Recording API List, download and delete call recordings Customers with Call Recording Pro Basic with a token You create a token at recording.dstny.se
Conversational Intelligence API Conversations, transcripts, summaries and insights, plus webhooks Customers with Dstny Copilot Token (Bearer) Your administrator creates a token at conversation.dstny.ai
Dstny Copilot MCP Let an AI assistant read your conversation data Customers with Dstny Copilot OAuth login An account owner turns it on in the app

Get started

Three steps for every API.

1. Check your agreement

Make sure you have the product behind the API, for example Dstny Analytics or Dstny Copilot.

2. Create access

Create a ticket or token as the table shows. Choose only the permissions you need.

3. Make your first call

Send the credentials in the header and test a simple call. 

Our APIs

Each API has its own credentials. Create them with only the permissions you need.

User API

Lets an application act as a user: control calls, read call state, search contacts and set presence and diversions.

API specificationPostman collection

Who: all customers.

Login: a ticket used as a Bearer token, valid for one year.

Access: the user signs in at bc.dstny.se, opens User view and creates a ticket under Tickets.

Analytics API

The same statistics as in Dstny Analytics, as data for your own reports, data warehouse or logging tool. Ready-made connectors exist for Power BI, Qlik and Excel.

API specification

Who: customers with Dstny Analytics.

Login: a JWT you get with an API ticket. Choose a ticket at organization level.

Access: an administrator creates the API ticket in reports.dstny.se.

Call Recording API

List recorded calls, download audio files and delete recordings, for example for archiving or a GDPR request.

API specificationPostman collection

Who: customers with Call Recording Pro.

Login: Basic authentication with an email address and a token.

Access: a Super User creates a token at recording.dstny.se under Configuration, Tokens.

Conversational Intelligence API

Fetch conversations, transcripts, summaries and insights from Dstny Copilot, and get a webhook when a conversation has been processed.

API specification

Who: customers with Dstny Copilot. The API costs nothing extra.

Login: a token used as a Bearer token.

Access: an administrator creates a token at conversation.dstny.ai under Settings, API. Webhooks are registered on the same page.

Dstny Copilot MCP

Connect an AI assistant such as Claude or Cursor so it can read your meetings and conversations, based on the signed-in user's permissions. Read only and in beta.

Documentation

Requires a login to Dstny Copilot.

Who: customers with Dstny Copilot.

Login: normal OAuth sign-in, no tokens to copy.

Access: off by default. An account owner or administrator turns it on in the app under Settings, Account, AI assistant connection (MCP).

Frequently asked questions

If an app should act as a single user, use the User API. Get statistics with the Analytics API, recordings with the Call Recording API and Dstny Copilot conversation data with the Conversational Intelligence API.

A User API ticket is valid for one year. Analytics, recording and Conversational Intelligence tokens have their own validity periods in each portal.

The Conversational Intelligence API costs nothing extra. The other APIs require the product behind them, for example Dstny Analytics or Call Recording Pro.

Normal outbound HTTPS on port 443 to Dstny addresses is enough. If your rules use IP addresses instead of names, contact us for the current addresses.

Usually the ticket or token has expired, lacks permission or is used against the wrong address.

Can't find what you're looking for?

Tell us what you want to build, and we'll help you find the right API and the right access.