APIs & webhooks
Plan controlled data exchange between your retail systems and the Vehoo workflow.
Reliable connections need explicit rules.
APIs exchange records; webhooks signal events. Neither removes the need to authenticate requests, validate data, handle duplicates and recover from temporary failure. Integration design should document these behaviours before production access is granted.
This page explains the integration approach. It is not a public developer API reference, and it does not imply that self-service production credentials are available.
A clear operational workflow.
Agree the rules, give each step an owner, and make exceptions visible.
What we establish together.
- A specific integration use case and the systems involved.
- Authentication, least-privilege access and credential rotation ownership.
- Idempotency, webhook validation, retries and reconciliation rules.
- A documented test and release process before live access.
A carrier might send the same delivery event twice. The receiving integration should recognise the duplicate and avoid sending two identical customer updates or completing the order twice.
This example explains the workflow; it is not a customer case study or a performance claim.
Your questions, answered.
Is there a public API documentation portal?
Not at present on this website. Discuss the integration need with Vehoo to establish the available interface and documentation.
How are credentials supplied?
Production access must follow the agreed secure onboarding process. Credentials should not be placed in storefront code or shared public files.
Can webhooks arrive out of order?
They can in many distributed systems. The integration should validate sequence and current state rather than blindly overwrite records.
What is idempotency?
It means a repeated request has the same intended effect as a single request, helping prevent duplicate actions.
Are custom endpoints possible?
Requirements can be assessed, but availability, development cost and maintenance are confirmed in the scope.
Retail software integrations
Connect existing POS, stock, payment and fulfilment systems where practical.
02Order management
Give each online order a clear status, a responsible person and a defined next step.
03Delivery tracking & notifications
Give customers clearer order progress from preparation to delivery.
A dependable connection needs more than a successful request.
Product changes, stock movements and order events need stable identifiers so both systems agree which record is being updated. We define the data shared, the permitted actions and the source of truth before connecting a merchant system to the online store.
Connections should handle repeated events, delays and unavailable services. For example, receiving the same order event twice must not create two picking tasks. The integration plan includes controlled access and a way to identify failed updates without exposing customer information in public logs.
Your systems can be part of the plan.
Explore platform-specific connection routes, supported data and the checks we make before launch. If your system is not listed, we can assess its API, connector or export options.
See what Vehoo could look like for your store.
Tell us about your business. We’ll start with the way you work.