Provider-independent compliance integrations
Velocerta is designed to consume information from authorised data providers through a structured adapter layer. This means the platform can connect to multiple providers without being architecturally tied to any single source.
Architecture approach
Each data provider integration is implemented as a discrete adapter that translates the provider's response format into Velocerta's internal compliance event model. This design means:
- The core compliance workflow is independent of any specific provider
- New providers can be added without redesigning the platform
- Responses from different providers can be recorded and compared side by side
- Provider-specific limitations or quirks are handled in the adapter layer, not in the compliance logic
Available
DVLA vehicle identity and tax data
Source: DVLA Vehicle Enquiry Service
Authorised DVLA vehicle identity and tax information retrieved during vehicle onboarding and scheduled monitoring. Data includes make, colour, fuel type, year of manufacture, tax status and tax due date.
Source information is displayed with its source and last-checked time. Scheduled checks can identify meaningful changes when updated information is returned by the provider.
- Vehicle identity: make, model, colour, fuel type, year of manufacture
- Tax status and due date
- Scheduled monitoring on a configurable frequency
- Last-checked timestamp recorded against the vehicle record
DVSA MOT history and status
Source: DVSA MOT History API
Authorised MOT status, expiry, test history, mileage, defects and advisories retrieved and recorded against vehicle records. Scheduled checks can identify meaningful changes when updated information is returned by the provider.
- MOT status and expiry date
- Full test history with dates and mileage
- Defects and advisory items per test
- Scheduled monitoring on a configurable frequency
CSV onboarding
Import vehicle records via structured CSV file. This is the primary onboarding method in the current pilot platform and allows organisations to begin using the platform without requiring additional provider connections.
The CSV format is documented and can be generated from most fleet management or licensing systems.
Email notifications
Outbound email notifications for alerts and case updates, routed to configured recipients based on organisation and alert type. Notifications are sent from notifications@velocerta.co.uk with support@velocerta.co.uk as the reply-to address.
Webhook events
Outbound webhook events for alert creation, case status changes and other compliance events. Webhooks are signed with HMAC to allow receiving systems to verify authenticity. Suitable for integration with existing case management or CRM systems.
Requires approved connection
The following integrations require a formal approval, commercial agreement and permitted-use authorisation before they can be activated.
Insurance monitoring
Insurance monitoring requires an approved MIB or authorised insurance-provider connection. Velocerta does not use or automate the public MIB checker.
Insurance monitoring is not currently connected. Manual policy references may be recorded against vehicle records for review purposes but are not independently verified.
Council licensing systems
Read and write connectivity to council and operator licensing platforms, enabling vehicle records to be synchronised and compliance events to be reflected in the licensing system of record. Requires agreement with the relevant licensing authority and system vendor.
Planned
Fleet management system integrations
Read connectivity to fleet management and telematics platforms to synchronise vehicle records and reduce manual data entry.
Additional notification channels
SMS notifications, additional webhook event types and potential integration with third-party case management and CRM systems.
Integration enquiries
If you represent a data provider, licensing system vendor or integration partner, we would welcome a conversation about potential integration.
Contact us at hello@velocerta.co.uk to discuss integration requirements.