Connect TOPdesk to Power BI and your Azure data warehouse
Service management data from Topdesk
Yres reads TOPdesk through the OData reporting API of your TOPdesk environment, not through the regular REST API. You enter the full domain of your environment; Yres turns it into the address of the reporting service. Sign-in uses the login name of an operator account and an application password you create in TOPdesk. Large results are fetched page by page through the OData nextLink. The data arrives in an Azure SQL database in your own Azure tenant, ready for Power BI.
At a glance
- Connection
- The TOPdesk OData reporting API (https://<domain>/services/reporting/v2/odata), not the REST API under /tas/api
- Sign-in
- Basic: the login name of an operator account with an application password, not the regular password
- Permissions in TOPdesk
- A permission group with the "REST API" and "Use application passwords" rights, plus read access to the data you want to expose
- Domain
- You enter the full domain, for example myorganisation.topdesk.net. Yres only adds https:// and the path of the reporting service
- Paging
- Automatic, through the feed's @odata.nextLink
- Where it runs
- On the Azure Data Factory cloud integration runtime; TOPdesk is a publicly reachable cloud service, so no self-hosted runtime is needed
- Where credentials are kept
- You enter them once; after that they sit in the Key Vault of your own Azure environment
What you arrange yourself
- 1Preferably create a separate operator account in TOPdesk for the connection.
- 2Give that account a permission group with the "REST API" and "Use application passwords" rights and read access to the data you need.
- 3Log in with that account, open the user menu in the top right, go to Application passwords and choose Add. Save the password immediately: it is shown only once.
- 4Add the Topdesk source in Yres with the full domain, the operator's login name and the application password.
When you need this — and when you don't
A standalone connector is enough if…
If the standard reports and overviews inside TOPdesk are enough, or a single Power BI report on service desk data alone, a data warehouse is more than you need.
Yres adds value if…
Yres earns its place when service desk figures must sit next to other sources, for example HR, property or financial data at a municipality, housing association or care provider, or when you want to follow over a longer period how data in TOPdesk has changed. The data warehouse keeps every changed version for that.
Frequently asked questions: Topdesk
Does Yres use the TOPdesk REST API or the OData API?
The OData reporting API. It provides a feed that Yres reads page by page. Yres does not use the REST API under /tas/api. The "REST API" right is still required in TOPdesk for the account the connection signs in with.
Why does my TOPdesk connection fail after entering the domain?
Check that you entered the full domain, so myorganisation.topdesk.net and not just myorganisation. The form does not append .topdesk.net, so otherwise the address it builds is wrong. Only letters, digits, dots and hyphens are allowed.
Which TOPdesk account does Yres need?
An operator account, preferably one that exists only for this connection. The account signs in with an application password you create under Application passwords. That password cannot be retrieved after creation; if you lose it, you create a new one.
Can I follow service desk performance trends over several years with Yres?
Yes, from the moment you start loading. For every row that changed between two loads, Yres keeps the old and the new version. That lets you look back at an earlier state in Power BI, even where TOPdesk itself only returns the current value.
Full technical description in the knowledge base →·Last reviewed:
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.