3.1.0 Automate
HomeIntegrityControlSolutionsManagement Center
  • Introduction
  • About this release
    • Release notes
    • Breaking changes
  • Flow of the request
  • Sending data to the API
  • Authenticating the client
  • Installation
  • Configuration API
    • Examples
  • Scheduler
Powered by GitBook
On this page
Export as PDF

Flow of the request

When a client invokes the API, the server initially cross-references the API configuration to determine if client authentication is required. If so, and if set up, authentication is processed through a PIPE. Only after successful authentication does the request get normalized and forwarded to the designated pipe for executing the core logic.

If the pipe executes without any errors, the response will carry an HTTP 200 status. Depending on the configuration and PIPE logic, the response body might include data.

On error API will return server 500 with potential error description. This can be changed using configuration.

PreviousBreaking changesNextSending data to the API