Changelog

This update expands Ordinavo Connect with CRM and Customer Operations context. External systems can import jobs with customer, location and contact information and inspect the results through ImportJobs, Route Suggestions and webhooks.

Added

• Inbound Target Import and Batch Import accept customer, location and contact DTOs.
• Customer Mapping through tenant- and source-system-scoped External IDs.
• New customer scopes: customers.map, customers.write and customers.read.
• Mapping status and mapping warnings for ImportItems, ImportJobs and monitoring responses.
• Route Suggestions can be created from ImportJobs and use mapped customer context.
• VisitReport webhook events with CustomerContext, including visit_report.approved and visit_report.follow_up_required.
• Billing webhook events as structured billing triggers, including billing.event_created. Ordinavo does not create invoices in this workflow.
• Webhook Payload Options for customer context, contact details, summary previews and billing details.
• Postman Collection, example payloads and public OpenAPI schemas for the new Connect DTOs.

Changed

• Import responses can include customerMapping when the API key has the required customer scopes.
• Webhook payloads can include CustomerContext for the source system of the integration client.
• CustomerNumber is read from the Customer record and is not used as an operational target identifier.

Integration note

Existing clients should continue to ignore unknown fields. Customer-aware imports require inbound.targets.write or inbound.targets.batch.write together with customers.map. Detailed mapping IDs are only returned with customers.read.

• API key authentication
• Inbound target import
• Batch import
• Import jobs
• Smart route suggestions from imported targets
• Outbound webhooks