Integrate in Minutes.
Ship Attribution at Scale.
One normalized webhook API. SHA-256 privacy by default. Sandbox access available to partners on request. The API surface below is the target contract for the v1 preview: current CSMS and ad-tech partners run against an early-access build today. Production scale-out coincides with the SOC 2 Type II audit currently underway.
Three-Step Integration
Target contract for v1 preview. Sandbox credentials are issued on approval during CSMS onboarding.
curl -X POST https://api.videoev.io/v1/webhooks/session-event \ -H "Authorization: Bearer <your_api_key>" \ -H "Content-Type: application/json" \ -d '{ "event_type": "session_start", "session_id": "ev_sess_f7a2b4c", "hashed_vehicle_token": "sha256:a3f4b2c8d9e1...", "charger_id": "site_xyz_port_2", "current_soc_percent": 18, "estimated_dwell_time_mins": 42, "network_id": "evconnect_west", "timestamp_utc": "2026-03-08T14:22:33Z" }'
{ "status": "queued", "ad_eligible": true, "matched_segment": "ev_buyer_high_intent", "recommended_creative_format": "video_15s", "estimated_inventory_window_mins": 42 }
Endpoints
Base URL: https://api.videoev.io
Bearer Token
All requests require an Authorization: Bearer <token> header. Tokens are environment-scoped (sandbox / production) and partner-scoped (CSMS, DSP, measurement).
Tiered by Plan
Sandbox & Production
Standard HTTP
Ready to build?
Request sandbox credentials and our integration team will work with you on CSMS onboarding. First-event turnaround depends on your CSMS and signal mapping; most partners ship a working event inside the onboarding call.
Platform Status
Where VideoEV is today.
VideoEV is in active pilot, not a fully productionized network. This strip is the single source of truth for the platform’s operational posture. If a page elsewhere reads as more productionized than this, trust this strip.