⚠️ Charges Config (EOL Apr'26)
🛠️ Partner API Alignment Migration
⚠️ This table will be deprecated in April 2026. Migrate to
FUTURE__charge_configs.
This table works with charges table merged on charges.id = charges__charges_config.charge_id
A charge config is included in this table if the following condition is met:
- the associated
charge_idis in yourchargestable
SQL: charges__charges_config
| Column Name | Data Type | Description |
|---|---|---|
| id | integer | Unique identifier for the charges config record |
| charge_id | integer | The main charge id. |
| firmware | string | The current charge point firmware at the time the charge was performed |
| is_reservation | boolean | Boolean determining whether a charge has a reservation or not. During a reservation the charge point is shown as busy to the public and the user is paying 50% of charging costs while reserved |
| reservation_min | integer | Minutes the charge point was reserved prior to the charge starting |
| native_schedule | integer | Serialized schedule configuration defined natively on the charge point. |
| scheduled_start_at | timestamp_ntz | Timestamp for when the charge is scheduled to start |
| scheduled_stop_at | timestamp_ntz | Timestamp for when the charge is scheduled to stop |
Updated 6 days ago
