Integrations
There is no public Setosys API.
Nothing to sign up for, no keys to request. If that is what you came for, this sentence saves you ten minutes — and the rest of the page explains what exists instead.
Why not
Because the software isn't ours to expose.
We build custom operational systems for a small number of businesses at a time. What we deliver belongs to the business it was built for, and its interfaces are shaped around how that business works rather than generalised into a service other people can buy access to.
If you are looking for a self-serve platform that turns a prompt into an application, this is not that. What we do is replace the software a business is currently stitching together, and then keep it running.
If you're a client
Your system's API is yours.
Every system we deliver has its own documented interface, built for the integrations that engagement actually needed. It is part of the handover along with everything else, and the credentials are in your name.
If you need that documentation again, or want a new integration added to something we built, speak to your Setosys contact rather than filling in a form here.
In practice
What we most often connect to.
Not a fixed list. What a project connects to gets decided in the first phase, based on what the business already runs — and the ones that matter are usually the ones already holding the data.
- QuickBooks Online / XeroInvoices, customers, chart of accounts, job costing
- Email and SMSClient notifications and reminders, sent from the client's own account
- Spreadsheets and exportsExisting operational data, migrated or synced during rollout
- Payment processorsWhere invoicing or collections are part of the workflow
- Internal databasesSystems already in place that a new one has to read from or write to
Tell us what you already run.
If you're weighing up whether a custom system could replace what you have, the integrations are usually what decides it. Name the tools and you'll get an honest read on whether it's straightforward.