Ordinavo Connect API v1

Scopes

Limit each Integration Client to the actions it really needs.

Scope reference

Scopes are assigned per Integration Client. A request must have the required scope for the endpoint. Missing scopes return HTTP 403.

ScopePurpose
integration.health.readCheck whether authentication works
inbound.targets.writeCreate or update single inbound targets
inbound.targets.batch.writeCreate or update multiple inbound targets in a batch
customers.mapMap imported records to existing customer, location and contact references
customers.writeCreate or update customers, locations and contacts during import
customers.readReturn detailed customer mapping objects and Ordinavo IDs in API responses
import_jobs.readRead import job status and item results
route_suggestions.createCreate draft route suggestions from imported targets
route_suggestions.readRead route suggestion metadata
webhooks.readRead webhook subscriptions
webhooks.manageCreate, update and disable webhook subscriptions
webhook_deliveries.readRead webhook delivery status

Customer mapping scopes

inbound.targets.write is required to import targets. Add customers.map to link incoming records to existing Ordinavo customer references. Add customers.write only when the integration is allowed to auto-create or update customers, locations and contacts. Add customers.read when the API response should include detailed mapping IDs.

Recommended default

Use stable external IDs and the customers.map scope first. Enable customers.write only for integrations that are trusted to maintain customer master data.

Missing scope response

{
  "error": {
    "code": "missing_scope",
    "message": "The integration client does not have the required scope.",
    "requiredScope": "inbound.targets.write",
    "correlationId": "7d97b0f5..."
  }
}