Delete an EVSE and its connectors

delete/v1/tenants/{tenant_id}/stations/{station_id}/evses/{evse_number}
Requires an API key

Synchronous. Refused with 409 transaction_active while one of its connectors charges, bill_open while an open bill names one, display_configured while a display is maintained for it (delete the display first) and station_last_evse for the station's only EVSE (delete the station instead). An EVSE that transactions reference is marked removed in the core instead of deleted (retained true), so their history keeps it; it leaves every read and its number stays taken. Replays with the same Idempotency-Key return the same result.

Path parameters

  • tenant_idintegerRequired
  • station_idintegerRequired
  • evse_numberintegerRequired
    The EVSE's number on the station (evse_number in station reads).
    Minimum 1 · Maximum 99

Headers

  • idempotency-keystringRequired

Returns · 200

  • station_idintegerRequired
  • evse_numberintegerRequired
  • deletedboolean
    Default true
  • retainedbooleanRequired
    true when transactions reference the EVSE: the core keeps it marked removed, so their history keeps its EVSE and connectors; it leaves every station read and its number stays taken.
DELETE /v1/tenants/{tenant_id}/stations/{station_id}/evses/{evse_number}
curl --fail-with-body -X DELETE "https://api.ivoracharge.com/v1/tenants/1042/stations/1/evses/1" \
  -H "Authorization: Bearer $IVORA_API_KEY" \
  -H "Idempotency-Key: order-2026-09-30-0001"
Response · 200
{
  "station_id": 1,
  "evse_number": 1,
  "deleted": true,
  "retained": false
}
Try it is not available here yetRequests from this page are off until the production API at https://api.ivoracharge.com is public. Use the code samples from your application server; Ivora grants production access. Keys are created in Developer tools.