Developer Documentation
Emobi Integration API — Developer Entry Point
REST API with OpenAPI 3.0 specification. OCPP WebSocket proxy endpoint for direct charger connections. Webhooks for all OCPP events — session start/end, station status, fault codes, meter values, demand response signals. SDKs for Python, Node.js, and Java. API access is issued after a deployment scoping call.
Quick Start
Three Ways to Get Started
REST API
Full CRUD access to stations, sessions, charging profiles, and alerts. OpenAPI 3.0 spec available for your team to build against. Request access to get your API key.
Webhooks
Subscribe to OCPP events: session start/end, station online/offline, fault codes (StatusNotification), meter values (MeterValues), and OpenADR demand response signals. Delivered as structured JSON to your HTTPS endpoint with HMAC-SHA256 signature verification.
OCPP Proxy
Connect chargers directly to Emobi's OCPP WebSocket endpoint. Emobi translates all OCPP messages and delivers normalized events to your REST API consumer.
Authentication
API Authentication Overview
Emobi API uses OAuth 2.0 client credentials for server-to-server integration. API key header authentication is also available for simpler integrations.
import requests # Exchange client credentials for access token response = requests.post('https://api.getemobi.com/oauth2/token', data={ 'grant_type': 'client_credentials', 'client_id': YOUR_CLIENT_ID, 'client_secret': YOUR_CLIENT_SECRET, 'scope': 'ocpp:read sessions:read' }) token = response.json()['access_token'] # Use token in subsequent requests stations = requests.get( 'https://api.getemobi.com/v1/stations', headers={'Authorization': f'Bearer {token}'} )
SDKs
Available Language SDKs
API Access
Ready to Build?
API access is provisioned after a deployment scoping call. We configure your OCPP WebSocket endpoint, set up your network namespace, and verify your webhook receiver. Contact the integration team to start the process.
Request API Access