Built around your process
Keep your systems. Make the work between them easier.
A customer request rarely stays inside one application. API Composer brings data and actions from existing systems together at the right moment. Manual exports, one-off scripts and extra screens need not become permanent workarounds.
What it does for you
Connect your applications
We configure calls, authentication and input for the systems you already use.
Bring results back into the process
A response from one system becomes useful input for the next step.
Integrations that can evolve
The exchange remains understandable and reusable when a process or application changes.
A familiar example
How it works in practice.
A request requires a ValidSign signature. Configure the call, supply the required data and retain the returned reference for subsequent steps. The workflow uses confirmed signing status to process a document or start a review or recovery action. The request and the business decision are separate, reusable building blocks.
Its place in Service Automation Suite
We connect the work between systems.
API Composer provides the connection. Data Flow Composer helps when data must first be combined or transformed; Automation Composer can then carry out the agreed action.
For integration administrators and builders
From API request to reusable process step.
API Composer is configurable: define the request, source data, body, output mapping and error rules. For example, a ValidSign request whose reference and outcome feed the rest of a request workflow.
Configure the request and authentication
Set the method, URL, query, headers and authentication. Use environment variables and inheritance where appropriate so configuration need not be copied per workflow.
Discover and map data
Inspect the response with Discovery. Use source fields, fixed values and body templates for input. Map the result to an entity or Data Context for downstream requests.
Distinguish success, functional errors and technical failures
Configure error rules by HTTP code and/or message, using functional or fatal classification and bounded retries where appropriate. In the workflow, separately define what the business outcome means: continue, request information, review or assign a ticket.
Test and reuse
Test representative inputs and responses, including missing data and rejections. Configure pagination and timeouts for the API. Reuse requests, sequences and mappings; Entity output can be registered as a named Deliverable.
The API determines which data and actions are available. A technical error rule does not automatically define a business decision: configure that follow-up with the other building blocks.
