Field sales APIs built for the messy middle between order and fulfilment.
Connect mobile field orders, CRM customers, warehouse stock and ERP status without hiding implementation boundaries behind a logo wall.
curl "https://portal.salesrepsoftware.co.za/api/v1/orders?acknowledged=false" \
-H "X-API-Key: $SALESREP_API_KEY" \
-H "Accept: application/json"Integration architecture
A deliberate hand-off, not a vague “two-way sync”
Choose ownership before writing code. SalesPro Hub captures the field workflow; your CRM, ERP or warehouse can remain authoritative where it already works.
CRM / customer master
Stable external identities and incremental tombstones
SalesPro Hub field workflow
Customers, outlets, submitted orders and rep activity
ERP / accounting / WMS
Fulfilment reference, status and physical stock
Documentation map
Start with the decision you are making
Start here
API reference
Field sales API reference
The complete public REST endpoint index for orders, inventory, CRM customers and Zapier triggers.
Read documentationSales order REST API
Poll submitted orders, acknowledge ERP receipt and return fulfilment status without duplicate processing.
Read documentationInventory sync API
Read stock, push absolute SKU quantities, audit movements and build retry-safe ERP inventory synchronisation.
Read documentationCRM customer sync API
Upsert customer records using stable external identities and consume cursor-safe incremental changes.
Read documentationEvents & automation
Signed sales webhooks
Receive order, inventory and recurring-order events with HMAC signatures, stable delivery IDs and bounded retries.
Read documentationZapier REST-hook integration
Subscribe validated Zapier catch hooks to retryable order, delivery, customer and completed-visit events.
Read documentationImplementation guides
Sage and Pastel API integration guide
A practical polling, webhook and hybrid recipe for connecting SalesPro Hub orders and inventory to Sage or Pastel.
Read documentationIntegration support and source-of-truth matrix
See exactly what is shipped, what requires middleware and which operational decisions must be made before launch.
Read documentationOperations
Integration notifications
Configure the email, mobile push and WhatsApp notification channels that accompany integration workflows.
Read documentationAPI errors and integration troubleshooting
Resolve authentication, permission, validation, rate-limit, webhook and reconciliation failures.
Read documentationTechnical evaluation
Advising a client? Here is the honest implementation boundary.
The public APIs are shipped. Named Sage, Pastel, Xero, QuickBooks and HubSpot connections still require the system-specific middleware and mapping stated in their guides. We do not label that work “native.”
Reliability model
Designed for retries, partial failure and reconciliation
Retry-safe identities
Stable ERP references, external CRM IDs and per-SKU inventory references make replays predictable.
Cursor-safe polling
Timestamp-and-ID cursors prevent records being skipped when updates share the same timestamp.
Signed delivery
HMAC-SHA256 webhooks include stable delivery IDs, timestamps and attempt numbers.
Tenant isolation
Credentials, queries and mutations are scoped to one organisation and checked on every request.
Operational limits are part of the contract
Professional includes 5,000 API calls per tenant per day. External endpoint groups are throttled to 60 requests per minute. Use cursors, bulk updates and webhooks rather than full high-frequency polling.
Still evaluating the architecture?
Use the integration readiness kit before writing middleware
Work through source ownership, immutable IDs, field mappings, failure recovery, reconciliation and native-versus-custom connector decisions.
Developer and technical buyer questions
Does SalesPro Hub have an API?
Yes. Professional and Enterprise plans include a versioned REST API for submitted orders, inventory, CRM customer identities and Zapier REST-hook subscriptions. Access uses revocable tenant-scoped API keys.
Can SalesPro Hub integrate with Sage or Pastel?
Yes, through a guided API workflow that polls submitted orders, stores the Sage or Pastel reference, returns fulfilment status and synchronises inventory by SKU. The Sage SDK or customer-specific middleware remains part of the implementation; it is not represented as a one-click connector.
How are duplicate integrations prevented?
Order acknowledgements, CRM external identities and inventory references are retry-safe. Incremental customer and order polling uses timestamp-and-ID cursors, while webhook and Zapier deliveries include stable delivery identifiers.
Are SalesPro Hub webhooks signed?
Yes. Outbound webhooks use HMAC-SHA256 signatures over the timestamp and raw body. Deliveries include a stable ID, attempt number and bounded retries, and failing endpoints are automatically disabled after repeated failures.
Is there a sandbox?
A separate public self-service sandbox is not currently claimed. The 14-day trial includes Professional API features and is the supported way to test with isolated trial data. Enterprise implementation environments can be scoped during onboarding.
Test the real integration surface
Use Professional API features for 14 days
Create scoped keys, push test stock, poll orders and verify signed webhook delivery.