Charge Keys
Table name: charge_keys
Enriched charge key records with associated user and team information for charging operations.
Combines charge key data with user and team details to provide comprehensive charging access
management. Filters to include only charge keys that belong to either a team or user context.
SQL: charge_keys
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | Primary key |
| Other IDs | ||
| team_id | INTEGER | Foreign key referencing the team that owns this charge key |
| user_id | INTEGER | Foreign key referencing the user that owns this charge key |
| partner_external_id | VARCHAR | External identifier used by the partner system for this charge key |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the charge key was originally created |
| updated_at | TIMESTAMP_NTZ | Timestamp when the charge key was last modified |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the charge key was deleted, null if still active |
| blocked_at | TIMESTAMP_NTZ | Timestamp when the charge key was blocked from use, null if not blocked |
| user_deleted_at | TIMESTAMP_NTZ | Timestamp when the associated user was deleted, null if user still exists |
| team_deleted_at | TIMESTAMP_NTZ | Timestamp when the associated team was deleted, null if team still exists |
| Filters | ||
| is_monta_network | BOOLEAN | Indicates whether this charge key can be used on the Monta charging network |
| is_roaming_network | BOOLEAN | Indicates whether this charge key can be used on roaming partner networks |
| is_operator_network | BOOLEAN | Indicates whether this charge key can be used on operator-specific networks |
| is_default | BOOLEAN | Indicates whether this is the default charge key for the associated user or team |
| is_user_charge_key | BOOLEAN | Indicates whether this charge key belongs to a specific user |
| is_team_charge_key | BOOLEAN | Indicates whether this charge key belongs to a specific team |
| Attributes | ||
| active_until | TIMESTAMP_NTZ | Timestamp until which the charge key remains valid for use |
| type | VARCHAR | Classification of the charge key type, such as RFID or mobile app |
| identifier | VARCHAR | Unique identifier string for the charge key used in charging sessions |
| name | VARCHAR | Human-readable name assigned to the charge key for identification |
| user_is_active_application_user | BOOLEAN | Indicates whether the associated user is actively using the application |
| user_is_active_team_owner | BOOLEAN | Indicates whether the associated user is an active team owner |
| user_is_active_team_member | BOOLEAN | Indicates whether the associated user is an active team member |
Data inclusion criteria
This table uses the operator's teams and users tables to find records belonging to either (or both)
Data flow
| Upstream tables | Downstream tables |
|---|---|
| users | --- |
| teams | --- |
Alignment
Partner API
This table aligns with the get/charge-auth-tokens endpoint of the Partner API
The partner API only includes non-deleted team charge keys, so you must exclude other rows.
where deleted_at is null and is_team_charge_keyUpdated 20 days ago
Did this page help you?
