New backend, changes to the User API

As part of the upgrade of our backend, there will be some changes to our User API. Please update your integrations wherever you use our User API, if you rely on anything that is changing.

Upgrade: the night before Wednesday 28 October 2026
The upgrade will be carried out during the night between Tuesday 27 and Wednesday 28 October 2026. The changes take effect from 28 October 2026 onwards.

The current backend is forward-compatible, so you can make the changes already now.

Creating a ticket for your own user

Previously, you could generate an md5 hash based on username, domain and password. This API endpoint has been changed to use HTTP Basic auth instead.

Before	md5 hash of username, domain and password
Now	HTTP Basic auth

Creating tokens for another user

The API endpoint for creating a user token for another user via an organization admin has changed. Going forward, this endpoint must be used:

POST /tickets/v1/{domain}/{user}

Where {user} is the user the user token is being created for.

Going forward, it is also a requirement that the token being created has exactly the same API permissions as the token used to create it.

Example: If an organization admin uses a token with e.g. CALLS and SMS, the new token created for the other user must also have CALLS and SMS.

Note: If you already use a Service Account to create tokens for users, you can continue to use that method.

API documentation

See our latest API documentation here: https://api-docs.connect.dstny.dk/

To see the documentation for the upcoming backend, click the "next" version of the documentation in the menu on the left-hand side.

Deprecated API endpoints

From 28 October 2026 onwards, the following endpoints will be removed from the User API. Please review your integrations and switch to the new endpoints where relevant.

1. Create and delete user tickets – "v0" endpoints

These endpoints will be removed:

POST   /api/tickets/{domain}/{user}
DELETE /api/tickets/{domain}/{user}/{ticketName}

New API endpoints have been introduced to manage user tickets, replacing the legacy method using password-based tickets.

2. Contacts Information API

All endpoints starting with /api/contacts/info will be removed.

This legacy API has been replaced with enhanced functionality in other APIs.

3. ACD/Attendant Group API

This endpoint will be removed:

POST /api/user/acd-attendant-group/{domain}/{user}/{group}/{group-domain}/agents/{agent}

4. ACD/Attendant Group API – "v0" endpoints

These endpoints will be removed:

GET /api/user/acd-attendant-group/{domain}/{user}/{group}/{group-domain}
GET /api/user/acd-attendant-group/{domain}/{user}

All API endpoints have been updated to version "v1".

5. Call Recording Control API

These endpoints will be removed:

GET  /api/call/recording/{domain}/{user}/list
POST /api/call/recording/{domain}/{user}/update/{id}

This API has been replaced with the Call Recording API.

6. Queue Statistics API – "v0" endpoints

These endpoints will be removed:

GET /api/queue/statistics/{domain}/{user}
GET /api/queue/statistics/{domain}

All API endpoints have been updated to version "v1" to better support supervisor authorization.

7. ACD/Attendant Group API – methods not supporting linked organizations

These endpoints will be removed:

GET  /api/user/acd-attendant-group/{domain}/{user}/{group}
POST /api/user/acd-attendant-group/{domain}/{user}/{group}/agents/{agent}

8. Distribution Group API – methods not supporting linked organizations

These endpoints will be removed:

POST /api/user/distgroup/{domain}/{user}/{grpid}/login
POST /api/user/distgroup/{domain}/{user}/{grpid}/logout