01
Choose resources
Define the charger, location, user, session, tariff, or reporting data required by the use case.
Connect charging to your systems
EV charging API for network, session, and partner workflows
Sock8 APIs expose agreed charging-network capabilities so customer portals, mobile apps, support tools, billing systems, and partner services can work with chargers and sessions without direct OCPP handling.
The integration layer is designed around explicit resources, permissions, and event ownership. APIs handle requested operations while webhooks notify downstream systems when important network or session state changes.
Who it is for
Built for teams accountable for live charging.
- CPO product and engineering teams
- Fleet and energy-management platforms
- Charger manufacturers and resellers
- Payment, CRM, ERP, and support integrators
Problems it solves
Replace operational blind spots with one system.
- Business systems coupled directly to OCPP
- Polling for session and charger updates
- Manual transfer of charging records
- No consistent partner authorization model
How it works
A clear path from connection to daily operation.
02
Assign access
Create the integration identity and limit it to approved operations and environments.
03
Call and subscribe
Use the agreed API operations and register webhooks for relevant state changes.
04
Reconcile
Store identifiers, handle retries and idempotency, and compare downstream outcomes with CSMS records.
Product view
See the operating detail behind the promise.
APIs and webhooks connect CSMS records to customer applications and interoperability partners without exposing charger protocol complexity.
Representative Sock8 product interface
Features
Capabilities included in the product scope.
- Network and charger resources
- Session and transaction data
- Remote-operation endpoints
- Tariff and customer workflows
- Event webhooks
- Environment-specific credentials
Protocols and interfaces
Designed to connect the charging stack.
HTTPSREST APIsJSONWebhooksOCPP 1.6JOCPP 2.0.1
Implementation or migration
Move from technical discovery to a controlled launch.
- 1
Use-case definition
Specify actors, events, data fields, system of record, latency, failure handling, and audit needs.
- 2
Contract review
Agree available endpoints, webhook events, permissions, identifiers, and environment boundaries.
- 3
Integration build
Implement authentication, request validation, idempotency, retries, logging, and reconciliation.
- 4
Production release
Complete end-to-end testing, rotate production credentials, and monitor initial traffic and failures.
Customer evidence
OCPI roaming enabled across three markets
3 markets · OCPI 2.2.1 roaming live
Wheelsdrive · Italy
The operator centralised billing while exchanging roaming sessions and CDRs with external partners.
Evidence shown is limited to the named deployment facts currently approved for this site.
Deployment
Choose the operating boundary.
API access is provided within an agreed Sock8 platform or customer-hosted deployment and separated by environment.
Pricing information
Scope the commercial model.
Standard integration access follows the selected platform scope. Custom endpoints, partner onboarding, dedicated environments, and unusual volume or support needs are quoted separately.
View platform pricingBuyer FAQs
Questions technical and commercial teams ask.
Is the EV charging API the same as OCPP?+
No. OCPP connects chargers to the CSMS; the business API exposes approved network capabilities to applications and partner systems.
Are webhooks available?+
Yes, for agreed events. Each integration should still implement signature checks, retries, idempotency, and reconciliation.
Can an API start or stop charging?+
Remote operations can be exposed when the integration is authorised and the connected charger supports the required command flow.
Is there a sandbox?+
Environment access and representative test data are agreed as part of the integration plan before production credentials are issued.
Can Sock8 build a custom endpoint?+
Custom API work can be scoped when the requirement is not covered by the standard integration surface.
Next step