ERP API Integration Explained: REST, Webhooks, Auth and Idempotency
A plain-English explanation of ERP API integration: REST APIs, webhooks, authentication methods, idempotency, pagination, rate limits and error handling.
Integration · CRM & Marketing
Overview
We integrate HubSpot's CRM APIs with the ERP, keeping each system authoritative for the data it does best.
01Data
| Entity | Direction | Notes |
|---|---|---|
| Contacts & companies | ⇄ Both | Matched by email and domain; ERP customer numbers written to HubSpot. |
| Deals | App → ERP | Won deals create ERP quotes or orders. |
| Products | ERP → App | Product library kept in sync for deal line items. |
| Orders & revenue | ERP → App | Order history and lifetime value as properties or custom objects. |
| Invoice status | ERP → App | Outstanding balance visible to account owners. |
02Use cases
Campaigns targeted by what customers buy.
Won deals flow into operations.
Sales sees orders and balances in HubSpot.
03 — Architecture
HubSpot webhooks notify changes to contacts and deals; the integration fetches full records via the CRM v3 APIs. ERP changes are pushed in batches using batch endpoints.
Custom properties or custom objects hold ERP data so HubSpot reporting and workflows can use it.
04Reliability
A HubSpot private app access token or OAuth app with only the required scopes, stored securely.
Property validation and association errors captured with record IDs and routed to an exception queue.
Retries respect HubSpot rate limits with backoff; deduplication via unique identifiers.
05 — Data mapping
| HubSpot | ERP |
|---|---|
| contact.email | Partner contact |
| company.domain | Partner company |
| deal (closedwon) | Sales order |
| line_item.hs_product_id | Product |
| custom property: erp_customer_id | Partner reference |
06 — Automation
07 — Security
Least-privilege scopes, encrypted credentials and consent-aware syncing of marketing contacts.
Related
Other integrations
Insights
A plain-English explanation of ERP API integration: REST APIs, webhooks, authentication methods, idempotency, pagination, rate limits and error handling.
How to integrate an ERP with eCommerce, CRM, payments and other systems: data ownership, integration patterns, middleware, error handling, monitoring and common failure modes.
How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.
FAQ
Yes, as properties or custom objects in HubSpot.
If HubSpot is your CRM, the ERP's CRM may not be needed; we design the split.
Matching rules on email and domain plus stored IDs on both sides.
Next step
Describe the data that needs to move and who owns it. We will propose a design with error handling and monitoring included.