Hello all,
The TimeXtender API Endpoints are built around Jobs in TX. Now that Jobs in TX are depreciated, how do we now retain the ability to trigger execution packages via API?
Please note I’m not talking about regular orchestration which can be achieved in TimeXtender Orchestration, but the cases where we need to be able to trigger TX via an API, as was possible with Jobs.
+5Hi
This is no longer possible since deprecating Jobs.
I will convert this to a product idea, to allow for triggering execution package execution via TimeXtender Orchestration via an API call
+5Delivered. The new Public Orchestration API (v0) lets you trigger execution programmatically — run process maps, start orchestration runs, and query logs over the API — restoring the API-triggered execution you had with Jobs. It shipped in TimeXtender Data Platform 26.2 (May 13, 2026). Generate an API key in the Portal under Admin > Security and permissions to get started.
Release notes: https://support.timextender.com/product-updates/timextender-data-platform-26-2-3927
Documentation: https://support.timextender.com/general-137/timextender-orchestration-api-3946
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
