Rate limits and operational monitoring
Handle shared API quotas, provider deferrals and uncertain submissions safely.
By HaulMatch · Updated
Integrations are in preview. Setup access depends on rollout and provider configuration. If your settings show integrations are not enabled, contact HaulMatch for availability. Contact us.
On this page
Shared request budgets
Default minute budgets are 500 requests per organisation, 100 per API key or MCP grant, and 30 writes per key or grant. Keys and AI clients share the organisation budget. Every MCP tool call consumes quota. Endpoint-specific limits also apply; operators can configure budgets for their environment.
Read X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (seconds until reset). Respect Retry-After on 429 and 503. Keep API credentials on your server.
Handle throttles and unavailable shared limits
If the shared limiter is unavailable, authentication, integration and write requests return 503. Retry after the indicated delay with the same original request or idempotency identifier. A timeout or disconnected response may have an uncertain outcome; reconcile the existing operation before creating another shipment, invoice, agreement or email.
Provider requests are queued under shared account budgets. Quota deferrals preserve failure-attempt budgets. Shopify cost throttles, MYOB quota errors and vendor Retry-After responses delay work automatically.
Inspect operational health
Company owners can review their delivery and operation logs in integrations. Staff with monitoring access can open Admin → System → Integration health for request traffic, throttles, queue due age, worker status, provider cooldowns and organisation/key usage.
The admin view refreshes every 10 seconds and labels unavailable or stale observations. Configured credentials do not establish successful live vendor access. Independent alerts require deployment and channel configuration by an operator.
Review uncertain submissions
An UNKNOWN outcome requires checking the remote record. Do not blindly repeat a creation. DocuSign status webhooks are preferred, with normal sent-agreement reconciliation spaced at least 20 minutes apart. Keep correlation identifiers stable and review paused, expired or revoked connections before resuming work.