Developer resources
Developer tools

Add an EVSE with its connectors

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

Synchronous: the response is the EVSE with its connectors' resource IDs. Connectors take the next OCPP 1.6 connector numbers on the station and are numbered 1, 2, ... on the EVSE; type, format, power_type, max_power_w (W), max_amperage_a (A) and max_voltage_v (V) describe each. A taken evse_number, including that of a removed EVSE transactions keep, returns 409 evse_number_taken. Assign tariffs as for any connector. No charger message is sent: the charger reports its own EVSEs. Replays with the same Idempotency-Key return the same result.

Path parameters

  • tenant_idintegerRequired
  • station_idintegerRequired

Headers

  • idempotency-keystringRequired

Request body

  • evse_numberinteger | null
    The EVSE's number on the station (OCPP 2.x evseId); omit for the next free number.
    Minimum 1 · Maximum 99
  • physical_referencestring | null
    Label printed on the EVSE, for example A or 2 (OCPI physical_reference).
    1–16 characters
  • connectorsarray of ConnectorInput
    Its connectors, numbered 1, 2, ... on the EVSE; one undescribed connector when omitted.
    Child attributes
    • typeenum | null
      OCPP 2.x connector type, for example IEC62196T1 (J1772), IEC62196T1COMBO (CCS1) or CHAdeMO.
      One of CHAdeMO, ChaoJi, DomesticA, DomesticB, DomesticC, DomesticD, DomesticE, DomesticF, DomesticG, DomesticH, DomesticI, DomesticJ, DomesticK, DomesticL, DomesticM, DomesticN, DomesticO, GBTAC, GBTDC, IEC603092Single16, IEC603092Three16, IEC603092Three32, IEC603092Three64, IEC62196T1, IEC62196T1COMBO, IEC62196T2, IEC62196T2COMBO, IEC62196T3A, IEC62196T3C, NEMA520, NEMA630, NEMA650, NEMA1030, NEMA1050, NEMA1430, NEMA1450, PantographBottomUp, PantographTopDown, TeslaR, TeslaS
    • formatenum | null
      One of Socket, Cable
    • power_typeenum | null
      One of AC1Phase, AC2Phase, AC2PhaseSplit, AC3Phase, DC
    • max_power_winteger | null
      Maximum power in W (watts), for example 7400 or 150000.
      Minimum 1 · Maximum 1000000
    • max_amperage_ainteger | null
      Maximum current in A (amperes).
      Minimum 1 · Maximum 2000
    • max_voltage_vinteger | null
      Maximum voltage in V (volts).
      Minimum 1 · Maximum 2000

Returns · 201

  • evse_numberintegerRequired
  • physical_referencestring | null
    Label printed on the EVSE.
  • station_idintegerRequired
  • connectorsarray of ConnectorRecordRequired
    Child attributes
    • idintegerRequired
      Connector resource ID; commands, bills and connector routes take it.
    • numberinteger | nullRequired
      OCPP 1.6 connector number on the station.
    • evse_numberinteger | nullRequired
    • evse_connector_numberinteger | null
      OCPP 2.x connector number on its EVSE.
    • statusstring | nullRequired
    • tariff_idinteger | nullRequired
    • typestring | null
      OCPP 2.x connector type, null when unknown.
    • formatstring | null
    • power_typestring | null
    • max_power_winteger | null
      Maximum power in W (watts).
    • max_amperage_ainteger | null
      Maximum current in A (amperes).
    • max_voltage_vinteger | null
      Maximum voltage in V (volts).
POST /v1/tenants/{tenant_id}/stations/{station_id}/evses
curl --fail-with-body -X POST "https://api.ivoracharge.com/v1/tenants/1042/stations/1/evses" \
  -H "Authorization: Bearer $IVORA_API_KEY" \
  -H "Idempotency-Key: order-2026-09-30-0001" \
  -H "Content-Type: application/json" \
  -d '{}'
Response · 201
{
  "evse_number": 1,
  "physical_reference": "string",
  "station_id": 1,
  "connectors": [
    {
      "id": 1,
      "number": 1,
      "evse_number": 1,
      "evse_connector_number": 1,
      "status": "string",
      "tariff_id": 42,
      "type": "string",
      "format": "string",
      "power_type": "string",
      "max_power_w": 1,
      "max_amperage_a": 1,
      "max_voltage_v": 1
    }
  ]
}
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.