Skip to main content
Solved

Does the TOPdesk History API provide access to all changes made to an incident, change, or other card?

  • July 20, 2026
  • 1 reply
  • 36 views

Forum|alt.badge.img

 

We are looking for a way to retrieve a complete audit trail through the API, including who made a change, what was changed, and when the change occurred. Is this information available via the History API, and are there any limitations regarding which events are recorded or accessible?

Best answer by Joost Oostindie

The complete audit trail is not available through the TOPdesk API.

There's no API that provides a full audit log containing all field changes, including who changed a value, the old and new values, and the exact timestamp for every modification. The available history endpoints are limited to specific objects and use cases.

If you need to track specific changes, my recommended approach would be to configure logging actions through Action Management. With these actions, you can define exactly which events you want to capture and which information should be stored by using variables. This gives you more control over what is logged, for example the user who performed the action, the changed values, timestamps, or other relevant details.

This approach is often more suitable when you need a custom audit trail for specific information.

1 reply

Joost Oostindie
Forum|alt.badge.img+9

The complete audit trail is not available through the TOPdesk API.

There's no API that provides a full audit log containing all field changes, including who changed a value, the old and new values, and the exact timestamp for every modification. The available history endpoints are limited to specific objects and use cases.

If you need to track specific changes, my recommended approach would be to configure logging actions through Action Management. With these actions, you can define exactly which events you want to capture and which information should be stored by using variables. This gives you more control over what is logged, for example the user who performed the action, the changed values, timestamps, or other relevant details.

This approach is often more suitable when you need a custom audit trail for specific information.