What Kind of APIs the Security Server Provides?
Â
The APIs represent different API styles: SOAP, REST and JMX. Some information, e.g. environmental and operational monitoring data, is available via multiple APIs representing different API styles. Instead, other information is available via a single API.
Below there's a list of the current Security Server APIs.
Message Exchange
Message exchange via X-Road is done using the X-Road message protocols that support REST and SOAP.
Meta Services
Meta services provide methods that can be used to discover what services are available within an X-Road instance and download service descriptions files (OpenAPI / WSDL).
More information:
https://docs.x-road.global/Protocols/pr-mrest_x-road_service_metadata_protocol_for_rest.html
https://docs.x-road.global/Protocols/pr-meta_x-road_service_metadata_protocol.html
Environmental Monitoring
Environmental monitoring provides technical monitoring information about the Security Server, e.g. details of the security servers such as operating system, memory, disk space, CPU load, running processes and installed packages, etc.
More information:
Operational Monitoring
Operational monitoring provides operational monitoring information and statistics about the Security Server, e.g. which services have been called, how many times, what is the average response time, etc.
More information:
Signed Document Download
An API for retrieving signed and time-stamped messages processed by the Security Server.
More information:
Healthcheck
The health check API can be used to ping the Security Server using HTTP to see if it is healthy and likely to be able to send and receive messages.
More information:
Management API
Management APIs provides access to all the administrative features of the Central Server and Security Server - all the features that are available in the UIs are available through the APIs too.
More information:
Related articles
Â
Â
Â