If the application can do it, so can you.
CubeERP and CubeERP API & Webhooks
A documented REST API and webhooks covering the whole system - the same interface the product itself is built on.
- Platform
- No per-connector licence
- 01234 672 617
Closed systems are a commercial strategy, not an engineering one. CubeERP exposes a documented REST API covering customers, quotes, orders, stock, production, purchasing and invoicing, with webhooks for events you need to react to. The application uses the same API, which means it stays current and complete rather than being a partial afterthought maintained separately from the product.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.
- Both ways
Full REST API
Read and write access across the system - customers, quotes, orders, stock, works orders, purchase orders, invoices and documents.
- Out of CubeERP
Webhooks
Events pushed as they happen - order created, goods received, works order completed, invoice raised - so integrations react rather than poll.
- Into CubeERP
Machine and device data
Shop-floor equipment, test rigs, scales and existing MES layers can post completions, results and downtime directly.
How it behaves
The detail that decides whether it is actually useful
Documentation that is current
An OpenAPI specification with examples, generated from the same definitions the application uses, so it does not drift.
Scoped access tokens
Tokens scoped to the endpoints and records an integration needs, revocable individually, with every call logged.
Stable and versioned
Breaking changes are versioned with notice. An integration you build should not stop working because we shipped a release.
Rate limits you can see
Published limits and clear error responses, so an integration behaves predictably instead of failing mysteriously under load.
Setting it up
Three steps, done during implementation
- 1
Create an API client in CubeERP and scope its token to what the integration actually needs.
- 2
Work against the OpenAPI specification in a sandbox environment before touching live data.
- 3
Subscribe to the webhooks you need rather than polling - it is faster and it is kinder to both systems.
Questions
What people ask about this one
No. The API is part of the platform. We do not charge per connector, per call, or for the privilege of integrating with your own system.
Yes, and they are welcome to. If you have an in-house team or an existing supplier, they can build the integration without going through us.
Yes. A separate environment with representative data, so integration work never touches live records during development.
Tell us. The API is extended as the product is, and gaps that block a real integration get prioritised rather than deflected.
Yes - bespoke integration work is available through Cube Systems and its sister company Crushed Ice. It is an option, not a requirement.
Related
Usually set up at the same time
- Power BI & ReportingDirect, read-only access to your CubeERP data for Power BI, Excel or any other reporting tool you already use.
- EDIElectronic data interchange with retailers, OEMs and distributors - orders and schedules in, despatch advices and invoices out.
- Microsoft 365Single sign-on with Entra ID, Outlook email and calendar, and documents where your team already keeps them.
API
Check the API detail before you commit
Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.