🧭✨Future Sponsored Charge Points (NEW)
✨ NEW TABLE - November 2025
🛠️ Partner API Alignment Migration
🧭 This table represents the post-migration state for
sponsored_charge_points.1️⃣ Migrate to this table by April 2026
2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix
Contains sponsored charge point relationships between charge point operators and teams. Links charge points to sponsoring teams and tracks sponsorship details including payouts and subscription settings.
SQL: FUTURE__sponsored_charge_points
Schema
| Column Name | Data Type | Description |
|---|---|---|
| Primary ID | ||
| id | INTEGER | primary_key |
| Other IDs | ||
| charge_point_id | INTEGER | References the associated charge point's unique identifier |
| team_id | INTEGER | References the sponsoring team's unique identifier |
| price_group_id | INTEGER | References the price group applied to this sponsored charge point |
| Timestamps | ||
| created_at | TIMESTAMP_NTZ | Timestamp when the sponsorship record was created |
| accepted_at | TIMESTAMP_NTZ | Timestamp when the sponsorship was accepted by both parties |
| updated_at | TIMESTAMP_NTZ | Timestamp of the last update to this sponsorship record |
| deleted_at | TIMESTAMP_NTZ | Timestamp when the sponsorship was terminated, null if active |
| Attributes | ||
| payout | NUMBER | The monetary amount paid to the charge point operator for this sponsorship |
| note | VARCHAR | Additional comments or details about the sponsorship arrangement |
| pay_for_subscriptions | BOOLEAN | Indicates whether subscription-based charging is covered under this sponsorship |
Changes from Last Version
- same schema
- inclusion criteria are changed to match API
Data Inclusion Criteria
- team_id is in among the operator's teams
- and charge_point_id is among id in the
FUTURE__charge_pointstable where the charge point matched on being sponwored, not owned by the operator
where
team_id in (
select id from FUTURE__teams
)
and charge_point_id in (
select id
from FUTURE__charge_points
where
-- Include charge points matched via sponsorship
(is_sponsor_operator_match = true or is_sponsor_parent_operator_match = true)
-- Exclude charge points already matched via ownership
and is_main_operator_match = false
and is_parent_operator_match = false
)
Data flow
| Upstream tables | Downstream tables |
|---|---|
FUTURE__charge_points | none |
FUTURE__teams |
Alignment
The sponsored_charge_points table
sponsored_charge_points table- one needs to align
teamsandcharge_pointstables, then recreate the filter aboe with the aligned rows.
Updated 4 days ago
