API integration: discovery, contracts and failure ownership
An integration connects two operating systems, not just two endpoints. Before implementation, define the records exchanged, the authority for each field, authentication, expected timing and
Journal
Connected systems
Connected systems need clear ownership of data and predictable behaviour when a request fails. Explore APIs, synchronization, webhooks and the decisions that keep records consistent.
Journal
Connected systems need clear ownership of data and predictable behaviour when a request fails. Explore APIs, synchronization, webhooks and the decisions that keep records consistent.
Keeping stock, prices and orders consistent between ERP and commerce
Consistency begins by naming the authority for each business fact. Stock, sellable availability, price and order status are not necessarily owned by the same system. Define direction, update
CRM synchronisation needs field ownership and conflict rules
A CRM sync should preserve meaning, not merely copy the newest row. Decide which system owns each field and which changes users are allowed to make locally. Record matching rules and deletio
Why webhooks need idempotency, retries and reconciliation
A notification arriving is not the same as a business action completing. Design for a sender to deliver an event again and for delivery order to differ from business order. Stripe's webhook
Connecting a legacy system through a new API
Begin by discovering which interfaces the old system actually supports and who is allowed to change it. A modern API can protect new applications from old details, but it cannot make an unre
Let's make something useful.
A first product, a difficult workflow or software that needs a fresh start. Tell us where you are.