Latest
Integration patterns
Designing an idempotent api integration: getting the keys right
Retries are unavoidable once two systems talk over a network. Idempotency keys are what stop those retries turning into duplicate orders, duplicate invoices and duplicate carrier labels — provided the keys are derived, scoped and stored properly.
Integration patterns
Designing a data flow you can prove: building an integration audit trail that holds up
Most integrations are designed to move data correctly. Far fewer are designed so that, nine months later, somebody can demonstrate exactly what moved, when, and why it produced the figure now sitting in the ledger.
Platform guides
What changes when you put OpenAI behind an internal API gateway
Routing model calls through an internal gateway changes the timeout budget, the retry rules, the cost record and the audit trail. Here is what has to be decided before the first application is pointed at it.
Platform guides
Bringing Anthropic Claude into a support desk: a claude api integration that keeps the audit trail
Language models are easy to demonstrate on a support desk and difficult to defend six months later. The difference is almost entirely in what you record at the moment each call is made.
Platform guides
Wiring Pipedrive to NetSuite Without a Second Source of Truth
Most CRM to ERP projects fail quietly: two systems end up holding slightly different versions of the same customer. This is how to design a Pipedrive NetSuite integration where every field has exactly one owner.
Platform guides
Zoho CRM Xero Integration: Closing the Gap Between Quotes and Invoices
The quote is agreed in the CRM and the invoice is typed again in the ledger. This is what a considered Zoho CRM and Xero integration has to decide before any code is written.