We connect your own software to business records over an authenticated HTTP API.
Sooner or later a business wants its data somewhere else — an internal tool, a data warehouse, a partner portal or a script that saves hours of clicking. A documented REST API with properly scoped credentials lets your developers, or ours, build on the system without touching its database or risking data they should not reach.
What we build with it
- Building an internal tool on top of business data
- Feeding a data warehouse
- Automating bulk operations
- Powering a customer or supplier portal
How it works
- An administrator creates an API credential and chooses what it may read or change.
- Your application sends HTTPS requests with that credential to the documented endpoints.
- The API checks the credential and its scope, applies the same business rules as the main application, and returns JSON.
- Every request is logged, and credentials can be revoked at any time without affecting other users.
Data exchanged
- Whatever the authorised scopes permit — typically masters, transactions and reports
What is needed to set it up
- API credentials issued for your account
- Scope selection limiting what the credential can reach
- A development environment for testing
Good to know
- Rate limits protect the system from runaway scripts. Bulk jobs are designed to page through data rather than request everything at once.
- Writes through the API follow the same validation as the application, so an integration cannot create records the screens would reject.
- API changes are versioned, so an update to the system does not break integrations that already work.
