If the application can do it, so can you.
CubeCRM and CubeCRM API & Webhooks
A documented REST API and webhooks covering the whole CRM - 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. CubeCRM exposes a documented REST API covering contacts, companies, enquiries, opportunities, quotes, activities, cases and custom fields, with webhooks for the 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. Your developers, your web agency or tools such as Zapier and Make can all build against it.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after switching over that one field never travelled.
- Both ways
Full REST API
Read and write access to contacts, companies, enquiries, opportunities, quotes, activities, cases and documents.
- Out of CubeCRM
Webhooks
Events pushed as they happen - enquiry received, deal stage changed, quote accepted, case opened - so integrations react rather than poll.
- Into CubeCRM
Automation platforms
Connect Zapier, Make and similar tools using webhooks and the API, for the long tail of apps you use.
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 under load.
Setting it up
Three steps, done during setup
- 1
Create an API client in CubeCRM 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 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 without going through us.
Yes, using Zapier’s webhook and API steps, and the same applies to Make and similar platforms.
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
- Website Forms & EnquiriesEnquiry forms on your website post straight into CubeCRM with the page, campaign and source attached - no more form emails to a shared inbox.
- Power BI & ReportingCRM data available to Power BI, Excel and other reporting tools, so sales data can sit alongside finance and operations in one set of reports.
- CubeERPCubeCRM shares its data model with CubeERP. When you need sales orders, stock, purchasing or production, it is an upgrade on the same records - not a migration.
API
Check the API detail before you commit
Send us the specifics - your mailboxes, your account codes, your phone system, your forms - and we will tell you exactly how it maps rather than promising it will be fine.
