Each API endpoint is documented on a separate page. Pages are version controlled.

Page version: , last updated:


This page lists every endpoint provided by the Consumer API which is a RESTful API consumed by the Tachyon Explorer UI and other Consumers. Although Tachyon has other APIs, the Consumer API is the only one supported for use by third party Consumers.

The URL used for requests is https://{tachyonConsumerServer}/Consumer/{request}

The text shown in example responses is spaced out for readability, normally they are compacted JSON on a single line with no white space between fields to minimize transmitted data.

API endpoints can be viewed and tested using a tool like the Postman, Fiddler or Advanced REST client extension for Chrome, but your chosen tool must support Windows Authentication.

In lab and test environments it's possible to configure Tachyon to use Basic Authentication over HTTPS using tools that only support this protocol where you would pass credentials explicitly rather than rely on NTLM challenge/response authentication.

This is useful where the account context in which the API call is made is not the account context in which you'd like the call processed. For example, when interacting with subsystems such as Workflow you may wish to make calls in the context of the requester and the responder but without having to switch interactive desktop sessions as the caller.

Exploring the API using the web browser

Although the Tachyon Consumer API is documented in the child pages to this page, you can also explore it using the inbuilt API documentation. This is available through your browser and managed through the Swagger subsystem by browsing to:

https://<tachyon server>/Consumer/swagger

Where <tachyon server> is the URL of your Tachyon Server, which redirects to the API reference page.

Each API is expandable, by clicking on it, you can view additional information about the API.

Tool settings


In Postman this setting and support for Windows Authentication, varies from version to version. For example, in the Chrome App version it's done automatically when No Auth option is selected.

In new standalone application, you should select 'NTLM Authentication (Beta)' and fill in the 'UserName', 'Password' and 'Domain' fields.


In Fiddler check Automatically Authenticate on the Composer->Options tab.

Advanced REST client

Google App Runtime for Chrome (ARC) requires the XHR extension turned on (the triple dot menu, top right of the window).

Error Conditions

If an error occurs, for example you use /Consumer/InstructionDefinitions/33333 when there are only 23 instruction definitions, the Consumer API returns a 404 error and XML error message, for example:

HTTP/1.1 404 Not Found 
 Cache-Control: no-cache 
 Pragma: no-cache 
 Content-Type: application/xml; charset=utf-8 
 Expires: -1 
 Server: Microsoft-IIS/10.0 
 X-AspNet-Version: 4.0.30319 
 Persistent-Auth: true 
 X-Powered-By: ASP.NET 
 Date: Thu, 04 Feb 2016 11:34:59 GMT 
 Content-Length: 142 
  "Message": "No HTTP resource was found that matches the request URI ' https://tachyondogfood.1e.local/Consumer/InstructionDefinitions/33333 '."

Consumer API SDK assembly

From v1.7 Tachyon provides an assembly to consume Consumer API. This assembly is versioned and wraps all the consumer API end points available in a version.

Release Notes

Api changes between Tachyon 4.0 and 4.1

There have been no API endpoints introduced, deprecated or removed in version 4.1.

Api changes between Tachyon 4.1 and 5.0

  • Consumer/PrincipalSearch method using GET verb is now deprecated and will be removed in a future version. Please use Consumer/PrincipalSearch using POST verb instead.
  • Consumer/PrincipalSearch method using POST verb has been added to augment Active Directory user and group search with the capability to request limiting the number of results returned, define sorting and explicitly specify type of AD objects to search (users, groups or both)
  • Consumer/SystemInformation/IsConsumerLicensed/Name/{name} method using GET verb has been added to allow checking consumer's licensed status by consumer name.
  • Consumer/SystemInformation/IsConsumerLicensed/Id/{id} method using GET verb has been added to allow checking consumer's licensed status by consumer Id.
  • Consumer/SystemInformation/LicensedConsumers method using GET verb has been added to allow retrieval of all licensed consumers.
  • Consumer/EventSubscriptionAssignments API has been introduced. It has 5 methods. This API and its methods have been introduced to support eventing mechanism.
  • Consumer/EventSubscriptions API has been introduced. It has 10 methods. This API and its methods have been introduced to support eventing mechanism.