Every ZofToken server has two different communication channels:
While the UDP traffic is in no way secret and an SDK is available so that other apps or components can operate directly as tokens, this document is meant to describe the second API as this is the one the organization would need to use to integrate ZofToken into their systems, whether this is a private installation or ZaaS.
In the introduction, the API is described as “REST-like” instead of simply REST because there have been a number of specific design decisions geared towards maximizing the simplicity of integration. From the start, we wanted the most basic operation needed for a system to integrate with ZofToken (checking the status of a token) to be a single HTTP GET request that could be equally simple to execute in the most cutting-edge development framework as it would be in a 15 year old legacy application.
With that in mind, the following is a list of these design decisions:
The API is provided in several different formats so that each developer who is working on an integration can choose whatever fits their workflow and tooling best.
For private ZofToken installations, it is still recommended to register for a free ZaaS subscription as this provides an instant sandbox for experimenting and testing.
The formats available for the API are:
This simple procedure, which shouldn’t take more than 10 minutes, will help you understand how the ZofToken solution works.