The overall purpose of the ITAS API is to provide external access to the ITAS system, both in terms of data and functionality. The API endpoints provide that point of contact and allow us to create a layer between ITAS and external usage. This enables Hivedome to create a re-usable set of ITAS objects for both point-to-point communication between systems (i.e. no human intervention) and new user interfaces (e.g. web pages, mobile apps and so on) built either by Hivedome or by clients. Although distinct in terms of meaning, this area of technology is sometimes referred to as Web Services.
Hivedome are adding new endpoints continuously - please see our online APIARY for documentation.
Web Services V1 allowed Hivedome to build an infrastructure to support fairly complex communications but was not effectively architected to allow for scaling out. It did allow us to develop reusable tooling such as the Events Engine and State Machine which will by and large stay as they are until they are migrated to V2 at a later stage
V2 has enabled Hivedome to start to define a model from scratch that will more accurately reflect the ITAS system as a whole.
This section provides information on the methods and best practices used by Hivedome to generate their suite of ITAS web services. It is intended for use by Business Analysis, Testers and Developers who wish to consume ITAS Web Services.