Skip to main content
All resources

Integration guide

How VehicleDesk connects to Shopmonkey

Understand the API, webhook, call-budget, credential, source-authority, data-freshness, and failure-state boundaries behind the Shopmonkey integration.

Subject owner
VehicleDesk Engineering
Last reviewed
2026-07-11
01

Use the official provider boundary

VehicleDesk connects server-side to the official Shopmonkey production origin. Provider credentials are not placed in the marketing site or authenticated browser bundle.

02

Budget every real request

Scheduled and manual sync jobs use explicit call budgets. Retries count as real HTTP attempts, quota snapshots remain visible, and work stops before the next request when the configured job budget is exhausted.

03

Verify webhook intake

Signed webhook events enter a replay-aware, bounded intake path and are processed asynchronously. A webhook acceptance response is not the same as successful downstream import.

04

Keep Shopmonkey authoritative

VehicleDesk organizes supported imported records and local workflow state. Source repair edits and financial finalization remain in Shopmonkey unless a separately approved narrow write workflow is introduced.

Related product detail

See how this guidance appears in VehicleDesk.

Open related workflow