01 / Webhooks
Receive events
vehicle.arrived reports an arrival; vehicle.updated reports a data update. Your service receives and processes these messages.
CRMMECH · For developers
An arrival event.
In your system.
Connect CRMMECH camera data to your own workflows. Webhooks deliver vehicle events, while the Pull API lets your application request data.
- 01Camera
- 02CRMMECH event
- 03Your HTTPS service
- 04CRM / 1C
Webhooks + Pull API
Arrival data for your workflows
This integration covers events related to camera-based vehicle recognition. Your developer decides how to match this data to your records and what your system should do when an event arrives.
02 / Pull API
Read data on request
The read-only API complements Webhooks: use requests to reconcile and recover missed data according to the documentation.
03 / Your logic
Connect a CRM or 1C
You need an HTTPS service on your side. Examples give developers a starting point; record matching and business logic must be implemented for your system.
From documentation to your first event
- 01
Define the workflow
Choose the events you need and how to check recognized data before changing records in your system.
- 02
Set up access
The workshop owner obtains an API key in CRMMECH integration settings. Check the options available for your account.
- 03
Build the receiver
Your developer creates an HTTPS endpoint, verifies HMAC-SHA256 and handles repeated events safely. The Pull API uses X-API-Key.
- 04
Test the exchange
Use the examples and test console in the documentation. Check signatures, redelivery, data reconciliation and error handling before going live.
Share the documentation with your developer
The official CRMMECH guide contains the current schemas, parameters, limits and error-handling rules.