API Integration

Q: How do I start using eMabler API v2?
A: Obtain an API key via eMabler Connect → Settings → Developers → Add API Key. Then use the API with the header x-api-key: <API_KEY> to authenticate.

Q: Which environments are available for API v2?
A:

• TEST: https://api.emabler.net/api/v2/cpo/

• STAGING: https://api-staging.emabler.net/api/v2/cpo/

• PRODUCTION: https://api.emabler.io/api/v2/cpo/

Q: How does API v2 differ from v1?
A: API v2 supports self-managed API keys, pagination, scalability for large datasets, and powers the Connect UI. It may include breaking changes during its beta phase (until Q4 2025).

Q: Can I test APIs interactively?
A: Yes. Use the Swagger UI via the documentation site or download the OpenAPI spec (/swagger.json) to import into tools like Postman.

Q: What is Push API and when should I use it?
A: The Push API delivers events (like start/stop, status updates) in real time via webhook, Kafka, or Azure Service Bus—ideal for event-driven integration workflows. REST polling introduces latency and load.

Q: How do webhooks work and how do I set them up?
A:

1. Enable Push API and webhook in eMabler Connect → Settings → Developers → Push API.

2. Provide a reachable endpoint with Authorization: <TOKEN> header.

3. eMabler sends events such as session, status, meter updates, and real-time RFID Authorize requests. Your service should reply with HTTP 200 to acknowledge.
   

Q: How does real-time RFID authorization with webhooks function?
A: When RealTimeAuth is enabled, eMabler sends a POST with "charger_id" and "rfid_tag_id". Your endpoint returns charging_allowed (boolean), optional rfid_tag_type, and a reason for rejection. eMabler then credits the session accordingly or blocks it. Fallback to OCPI occurs if configured.

Q: How are API permissions managed?
A: API permissions mirror those of the operator who created the key. Use role-based access, and requests will return errors if a user lacks the required permission for a specific endpoint.

Q: What should I do if webhook events stop delivering or fail?
A: Verify your endpoint responds to GET or POST with HTTP 200. Monitor retry queues and validate network reachability. Rotate or update credentials if your endpoint changes. Fallback (e.g., polling via REST) may need to be configured.

Q: Should I use API v2 in production now?
A: Yes, but keep in mind that v2 is currently in beta. It is stable for most use cases, but eMabler reserves the right for breaking changes before general release (state planned for Q4 2025).