Best Practices and FAQs
Recommendations and answers to common questions when integrating with the Driver Events API.
Follow these best practices when implementing and testing your Driver Events integration.
Follow the Recommended Event Workflow to provide a consistent view of the transfer as it progresses.
Include latitude and longitude with Driver Events when available. You can also send DRIVER_LIVE_LOCATION periodically during the transfer.
The occurredAt timestamp should represent when the event actually happened and must use ISO 8601 format. We recommend using local time with the correct UTC offset.
Use the staging environment to test your implementation and verify that Driver Events are being received correctly. For detailed guidance, please refer to Setup, Authentication & Testing page
Confirm your production setup with your Suntransfers contact before going live.
No. Always use the original booking reference provided by Suntransfers, without any suffixes.
- Correct:
SUNTR_YZ1234 - Incorrect:
SUNTR_YZ1234/1,SUNTR_YZ1234-LEG1,SUNTR_YZ1234-2
If your system uses extended references per transfer, map them back to the original Suntransfers booking reference when sending Driver Events.
Use the timestamp of when the event actually occurred. Do not use the scheduled pickup or drop-off time.
Example:
Scheduled pickup time:
2025-07-25T15:30:00Driver actually departed at:
2025-07-25T15:48:00The occurredAt value should be
2025-07-25T15:48:00, as this represents when the event actually occurred.
Support & Contact
If you need help during the integration:
Contact your Suntransfers Supplier Manager.
Contact [email protected] and include:
- Your supplier code
- A short description of the issue
- Sample payloads or error messages, when available
Updated 5 days ago