Skip to content
Logistics & shipping

enode.io

Enode sandbox and mock API

Download [OpenAPI 3.0 Specification](/OpenAPI-Enode-v1.4.0.json) Download [Postman Collection](/Postman-Enode-v1.4.0.json) The Enode API is designed to make smart charging applications easy to develop. We provide an abstraction layer that reduces the complexity when extracting vehicle data and sending commands to vehicles from a variety of manufacturers. The API has a RESTful architecture and util Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
28
Collections
-
Event types
-
Start this simulation
example request
curl https://your-enode.slurry.io/chargers \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.3.10.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 28.

  • GET/chargers
  • GET/chargers/{chargerId}
  • POST/chargers/{chargerId}/charging
  • GET/charging-locations
  • POST/charging-locations
  • GET/charging-locations/{chargingLocationId}
  • PUT/charging-locations/{chargingLocationId}
  • DELETE/charging-locations/{chargingLocationId}
  • GET/health/ready
  • GET/health/vendors
  • GET/me
  • DELETE/me/vendors/{vendor}