Skip to main content
Toronto roots. Digital possibilities.[email protected]

The Unicorn blog

Questions to answer before building an API integration

Digital cloud linked to database, code, security and synchronization icons

Connecting two systems is more than moving a few fields from one place to another. The integration needs to behave predictably when information is missing, a service is unavailable, or the same event arrives twice. A short design discussion before implementation can expose these decisions while they are still easy to change.

Decide which system owns each value

List the records and fields that will move between systems. Identify the authoritative source for each one and whether updates travel in one direction or both. If two systems can edit the same value, agree how conflicts will be resolved instead of quietly letting the last request win.

Define the expected timing

Some workflows need a prompt update; others can run on a schedule. Write down what an acceptable delay looks like and what should happen if that delay is exceeded. Consider the external service’s limits and the amount of data you expect to process, especially during an initial import.

Plan for repeated and failed requests

A retry should not create another order, another contact, or another notification unintentionally. Agree how records will be identified and how duplicate events are recognized. Distinguish a temporary failure from a rejected record, and decide when human review is needed rather than retrying indefinitely.

Make operations understandable

Record enough information to investigate a failure without exposing credentials or unnecessary personal data. Identify who receives alerts, where failed items are reviewed, and how a corrected record is resubmitted. A dashboard is only useful when someone knows what action to take from it.

Agree on change ownership

Third-party APIs and business processes change. Document the integration’s dependencies, credentials owner, and test scenarios. Decide who reviews changes to either system and how they reach production. Include a way to pause the integration when continuing would make a data problem worse.

Make the next step practical

Have a question about your own platform? Plan an integration with us and tell us what you would like to improve.