Integrations · API & webhooks
On the roadmapFor every system we don't have a connector for
A versioned REST API and signed webhooks are planned as the general answer for other systems. They'll read the data Nexus365 owns, subscribe to changes, and push their own data in through the same pipeline as file imports, with the same duplicate protection.
What it connects
What the connection carries
REST API
Documented, versioned endpoints for products, stock, orders and customers, scoped to one organisation.
Webhooks
Signed event notifications with retries, plus idempotency keys so duplicates are harmless.
API keys
Keys scoped to one organisation, stored encrypted and rotatable.
Health
Last delivery, failures and retries for every connection.
Before you start
What you'll need
- A developer, or a partner who builds integrations
- An admin to create the API key
What we don't claim
- The API and webhooks are on the roadmap and not available yet.
How to connect
How the connection will work
- 1
Create a key
An admin creates an API key scoped to your organisation.
- 2
Read and write
Call the API for the data Nexus365 owns, or push your system's data in.
- 3
Subscribe
Register webhooks for the events you care about and verify each signature.
- 4
Monitor
Watch deliveries and failures in the integration health view.
FAQ
API & webhooks questions
Can't find your system?
Tell us what you run today. We build connectors for the systems our customers actually use, so your answer decides what comes next, and we'll tell you honestly whether file import or migration covers you in the meantime.
See how Nexus365 fits next to what you run today
See Nexus365 with your own workflows in a guided demo, or explore the interactive demo yourself.
Or open the interactive demo — no account needed.