Built around your process
A clear entry point for collaboration.
When a supplier, customer or application sends an update, the information should reach the right place immediately. Endpoint Composer provides a managed entry point. Together we define the required data, access and handling of each request.
What it does for you
Clear input requirements
Define the data needed so the next step does not start with detective work.
Controlled access
Configure how each consumer or partner may use the entry point.
Give a useful response
The submitting party learns whether its request was received and processed.
A familiar example
How it works in practice.
Combine TOPdesk service data with central customer relationships and prepare the agreed selection in a Service Automation Suite data object. The customer reads it through a configured endpoint without direct access to TOPdesk. Another endpoint can receive supplier receipt data; a separate workflow defines its validation and processing.
Its place in Service Automation Suite
We connect the work between systems.
Endpoint Composer provides the entry point. Other Service Automation Suite components can then enrich data, update systems and organise follow-up.
For integration administrators and builders
A managed way to publish and receive your data.
API Composer calls another API. Endpoint Composer makes a configured Service Automation Suite data object accessible to a customer, supplier or application. You select methods and access; configure subsequent processing and business decisions separately.
Share service data with a customer
Combine service data and customer relationships in a data flow. Prepare only the agreed selection in the published object and give the consumer read access. The customer does not need direct access to the source system.
One data foundation for several consumers
Prepare information for BI or other applications and reuse central definitions and relationships. Configure a suitable data object and endpoint for each purpose instead of having every consumer combine all sources again.
A supplier reports receipt or delivery
Let a supplier submit agreed data to an object. A separately configured process checks references and confirmation and then updates the relevant TOPdesk activity, for example. Receiving data is not automatically proof of completed execution.
Define the data object and scope
Choose the Service Automation Suite object to publish. Configure permitted customer selection and content beforehand. An API key is not an automatic customer filter and does not itself determine which records belong to a consumer.
Select methods and keys
Configure GET for reading and enable POST, PUT, PATCH or DELETE only when needed. For write methods, choose key fields that identify records. Object endpoints do not support every field type.
Manage security profiles and API keys
Assign a security profile to the endpoint or inherit it from its folder. Manage named API keys with expiry dates. A key on a profile grants access to all endpoints using that profile, so scope profiles deliberately.
Test access and processing separately
Test permitted and denied access, read and write methods and existing-record identification. Then verify separately configured processing, feedback and error handling. An endpoint can be disabled without deleting its configuration.
