Inbound API for services
Introduction
With Patchworks standard integrations, you define a service with one system (a connector) configured as the source and another as the destination. Patchworks suggests field mappings between the two, but these can be tweaked as required.
Using an Inbound API Connector, you can configure a custom entity to define what information Patchworks should expect to receive in a payload from your bespoke system. Once configured, you specify this connector as the source in a Patchworks service, with another standard connector defined as the destination.
As part of this, you define your preferred URL for API access. This means that you can create a managed set of API endpoints for your services, without reinventing the wheel - all completely code-free with error-handling, and guaranteed delivery.
Where to start?
The steps are:
Last updated