Interactive example · sample data
Follow an update from source application to destination.
An application programming interface (API) lets one application ask another to do something and return a response. An event announces a change; each receiving application is responsible for acting on it.
CRM means customer relationship management: software for customer records. ERP means enterprise resource planning: software for business records and processes.
U-204 · The receiving system confirms the result
Portal
CRM
Connection between applications
Business system / master record
Shared information
POST /record-updatesResponse: U-204 accepted- Payload
- request: R-204; status: reviewed; update: U-204
- Source owner
- The portal manages the request’s review status
- Destination
- The ERP system manages the business record
- Exchange status
- The receiving system confirms the result
Identity / API
Only the service allowed to update request R-204 may call the destination interface. User access and service access have distinct responsibilities.
The sending application waits for a response. If the receiving service is unavailable, the request stays pending.
Discuss the systems you need to connect →Try the systems lab →Inspect related responsibilities →What we can build with you
Agreed rules for exchanging information, a working integration and tools to monitor it after deployment.
- Design the exchange
- Review how your systems share information and which system manages each record. Choose direct requests, events or scheduled transfers to fit the task.
- Build a dependable interface
- Agree on the information exchanged, access permissions and how to handle errors or repeated updates. If a required service is unavailable, show the work as pending rather than successful.
- Deploy in the right environment
- Test the settings and access permissions, and agree who will run and support the integration. We use Microsoft technologies and Azure where they fit the project.