Log inTalk to us
Developer tools

Assign a tariff to a connector

put/v1/tenants/{tenant_id}/stations/{station_id}/evses/{evse_number}/connectors/{connector_id}/tariff
Requires an API key

Synchronous. Links the connector to one of the project's active tariffs (the core's own connector tariff link; no charger message is sent). A tariff that does not exist in this tenant returns 404 tariff_not_found, an archived one 409 tariff_archived. Refused with 409 transaction_active (details.transaction_ids) while a transaction charges on the connector, because the price must not change under a driver; assigning the tariff it already has changes nothing (changed false). Needs stations:write and tariffs:write. Recorded in the audit log with the previous and new tariff. Replays with the same Idempotency-Key return the same result.

Path parameters

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

Headers

  • idempotency-keystringRequired

Request body

  • tariff_idintegerRequired
    An active tariff in this tenant (id from the tariff routes).
    Greater than 0

Returns · 200

  • connector_idintegerRequired
  • station_idintegerRequired
  • evse_numberintegerRequired
  • tariff_idinteger | nullRequired
    The tariff new sessions on this connector are priced by; null when none is assigned.
  • previous_tariff_idinteger | null
    Set by a change: the tariff the connector had before; null when it had none or on a read.
  • changedboolean | null
    Set by a change: false when the connector already had this assignment.
PUT /v1/tenants/{tenant_id}/stations/{station_id}/evses/{evse_number}/connectors/{connector_id}/tariff
curl --fail-with-body -X PUT "https://api.ivoracharge.com/v1/tenants/1042/stations/1/evses/1/connectors/1/tariff" \
  -H "Authorization: Bearer $IVORA_API_KEY" \
  -H "Idempotency-Key: order-2026-09-30-0001" \
  -H "Content-Type: application/json" \
  -d '{
  "tariff_id": 42
}'
Response · 200JSON
{
  "connector_id": 1,
  "station_id": 1,
  "evse_number": 1,
  "tariff_id": 42,
  "previous_tariff_id": 1,
  "changed": false
}
Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com

Paste a production api key (iv_live_…). Create keys in Developer tools. The key stays in this page's memory, is sent only to https://api.ivoracharge.com and clears when you reload. Test keys are refused.

PUT is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.