An API on your product
When a customer asks to connect your product to theirs, there is a documented, authenticated, versioned interface to point them at — not a promise to build one.
Extensibility
If it has an API, your application can use it.
No catalogue covers everything. What matters more than the list above is that the list is not a limit.
Every integration on this site was once "something a customer asked for". The catalogue tells you what we have already done, not what is possible. If a service has an API, your application can talk to it. If it does not — if it is a closed product with no way in, or the vendor forbids it — you will hear that in the first conversation rather than after planning around it.
Off until you need it. Turning it on is a toggle — not a project, not a rebuild. See how capability arrives as you grow.
Providers
What we connect to
Available means built and running in production today. On request means we will build it for your application — it is not pre-built, and we will not imply otherwise.
Available
- Public REST APIDocumented, authenticated, versioned
- Outbound webhooksWith retries and delivery logs
- Scheduled imports & exportsCSV, SFTP, or a direct feed
On request
- Zapier
- Make
- n8nSelf-hosted, where data must not leave
- Anything with an APITell us the service and we will tell you honestly
What you get
The part that is not just an API key
Webhooks out
Your application notifies other systems as things happen, with retries, signing and a delivery log so failures are visible rather than silent.
Scheduled exchange for older systems
Plenty of important software has no modern API. A nightly file over SFTP is unglamorous and works.
No-code bridges
Zapier or Make so your team can wire up the long tail themselves without waiting on us.
A straight answer when something will not work
Some vendors have no API, or forbid this use. We say so before you plan around it, which is cheaper for everyone.
For example
What this looks like in practice
A customer wants to integrate with you
They ask for an API on the pilot call. Having one, with documentation, is often what turns a pilot into a rollout.
A system nobody has heard of
The industry-specific software your business actually runs on. If it has an interface, it can be connected.
The long tail
A dozen small automations that are not worth building individually, handled through Zapier by the people who want them.