Charge Points

🛠️ Partner API Alignment Migration

🧭 This table represents the post-migration state for charge_points.

1️⃣ Migrate to this table by April 2026

2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix

Contains charge point data filtered and transformed for specific partners. This model filters charge points based on operator relationships (direct, parent, sponsor, parent sponsor) and enriches the data with additional partner-specific fields.

SQL: FUTURE__charge_points

Schema

Column Name	Data Type	Description
Primary ID
id	INTEGER	Primary key
Other IDs
team_id	INTEGER	ID of the team that owns/manages this charge point
user_id	INTEGER	ID of the user associated with this charge point
charge_point_model_id	INTEGER	References the model specification for this charge point
operator_id	INTEGER	Direct operator ID managing this charge point
parent_operator_id	INTEGER	ID of the parent operator organization if applicable
charge_point_site_id	INTEGER	ID of the physical site/location where charge point is installed
country_id	INTEGER	ID reference for the country
country_area_id	INTEGER	ID reference for the geographic sub-region
price_group_id	INTEGER	ID of the associated pricing group
cost_price_group_id	INTEGER	ID of the cost pricing group
roaming_price_group_id	INTEGER	ID of the roaming pricing group if applicable
meter_id	INTEGER	ID of the associated energy meter
grid_service_provider_id	INTEGER	ID of the electricity grid service provider
Timestamps
last_connected_at	TIMESTAMP_NTZ	Timestamp of the most recent successful connection
disconnected_at	TIMESTAMP_NTZ	Timestamp when the charge point was last disconnected
created_at	TIMESTAMP_NTZ	Timestamp when the charge point record was created
updated_at	TIMESTAMP_NTZ	Timestamp of the last update to this record
deleted_at	TIMESTAMP_NTZ	Timestamp when the charge point was marked as deleted, if applicable
integration_deleted_at	TIMESTAMP_NTZ	Timestamp when the integration was removed/deleted
active_at	TIMESTAMP_NTZ	Timestamp when the charge point became active
last_active_at	TIMESTAMP_NTZ	Most recent timestamp of charge point activity
first_active_at	TIMESTAMP_NTZ	Initial timestamp when charge point first became active
Filters
is_roaming_charge_point	BOOLEAN	True when charge point supports roaming access from other networks, false for network-only access
is_active	BOOLEAN	True when charge point is operational and available for use, false when offline or disabled
is_main_operator_match	BOOLEAN	Indicates direct match with specified operator_id
is_parent_operator_match	BOOLEAN	Indicates match with parent operator relationship
is_sponsor_operator_match	BOOLEAN	Indicates match with sponsor operator relationship
is_sponsor_parent_operator_match	BOOLEAN	Indicates match with sponsor's parent operator relationship
is_deleted_pii	BOOLEAN	Indicates if a row has PII that have been nullified
legacy_alignment_flag	BOOLEAN	Combines multiple conditions ((1.) charge point team is not demo, (2.) if there are sponsorship relationships, at least one is non-deleted, and (3.) at least one integration is not deleted) to flag rows that were present in prior version of this model.
Attributes
partner_external_id	VARCHAR	External identifier used by the partner system
team_partner_external_id	VARCHAR	Partner's external identifier for the team
external_id	VARCHAR	External identifier used for integration purposes
operator_name	VARCHAR	Name of the direct operator managing the charge point
serial_number	VARCHAR	Manufacturer serial number of the charge point
integration_state	VARCHAR	Current state of the integration (e.g. connected, disconnected)
cable_plugged_in	BOOLEAN	True when a charging cable is currently connected to the charge point, false when disconnected
name	VARCHAR	Display name of the charge point
identifier	VARCHAR	Unique business identifier for the charge point
state	VARCHAR	Current operational state of the charge point
visibility	VARCHAR	Controls whether the charge point is visible to users
show_on_map	BOOLEAN	True when charge point should appear on public maps, false when hidden from map display
type	VARCHAR	Type/category of charge point
note	VARCHAR	General notes about the charge point
operator_note	VARCHAR	Notes specific to operator usage/maintenance
charge_point_site_name	VARCHAR	Name of the site where charge point is located
address1	VARCHAR	Primary street address
address2	VARCHAR	Secondary address line if applicable
address3	VARCHAR	Additional address details if needed
city	VARCHAR	City where charge point is located
zip	VARCHAR	Postal/ZIP code of the location
country	VARCHAR	Country name where charge point is located
country_area	VARCHAR	Name of geographic sub-region (state/province)
location	VARCHAR	Formatted location string
longitude	NUMBER	Geographic longitude coordinate
latitude	NUMBER	Geographic latitude coordinate
max_kw	NUMBER	Maximum power output capacity in kilowatts
total_kwh	NUMBER	Total energy delivered in kilowatt-hours
model_name	VARCHAR	Name of the charge point model
brand_name	VARCHAR	Manufacturer/brand name
max_reservation_min	INTEGER	Maximum reservation time allowed in minutes
smart_charge_setting	VARCHAR	Configuration for smart charging features
smart_charge_priority_price	NUMBER	Priority score for price optimization in smart charging
smart_charge_priority_co2	NUMBER	Priority score for CO2 optimization in smart charging
smart_charge_priority_renewable	NUMBER	Priority score for renewable energy usage in smart charging
connector_count	INTEGER	Number of charging connectors available

Changes from Last Version

November 2025:

This table was significantly expanded to match the wealth of information in the Partner API Charge Points endpoint.

January 2026:

We removed row duplication in the legacy model and as a result, removed some row and columns vs the legacy pre-migration model. The legacy table included duplicated rows on the primary key (cp_id in the legacy model, id in the new model) in cases where a charge point had multiple sponsored charge point relationships.

The newest version of this model removes this duplication the id column is a truly unique primary key. One can still find both sponsorship relationships in the future__sponsored_charge_points model.

With the removal of the row duplication, two columns related to the sponsored charge points data were no longer relevant and were removed.

New columns (29):

Integration timestamps: integration_state, cable_plugged_in, last_connected_at, disconnected_at, integration_deleted_at
Show on map: show_on_map,
Notes: note, operator_note
Location enrichment: country_id, country_area_id, country_area, location
Energy/Power: total_kwh
Pricing: price_group_id, roaming_price_group_id
Operations: max_reservation_min, connector_count
Infrastructure: meter_id, grid_service_provider_id
Operator matching flags: is_main_operator_match, is_parent_operator_match, is_sponsor_operator_match, is_sponsor_parent_operator_match
Legacy alignment: legacy_alignment_flag

Renamed columns (4):

cp_id → id
cp_name → name
cp_model_name → model_name
cp_brand_name → brand_name

Removed columns (4)

sponsored_operator_id
sponsor_parent_operator_id
sponsored_price_group_id
sponsored_charge_point_id

Data inclusion criteria

The team associated with the charge point is not 'demo'
and
- the team's operator_id or partner_operator_id matches the operator
- or the sponsoring team's operator_id or partner_operator_id matches the operator

Data flow

Upstream tables	Downstream tables
none	`FUTURE__charges`
	`FUTURE__failed_charges_info`
	`FUTURE__sponsored_charge_points`

Alignment

Partner API

aligns with Partner API get/charge_points endpoint
Partner API param includeDeleted mut be set to true
Data in FUTURE__charge_points must be filtered where (is_main_operator_match=true or is_parent_operator_match=true) to match the API, as the API does not include sub-operators.

The `charge_points` table

To match charge_points filter FUTURE__charge_points by where legacy_alignment_flag = true