Change Log
2025 - W26
- This week we are releasing many overdue items from the promised roadmap.
- Many of the items were in fact already released, but now we are announcing them. Documentation is also being updated to reflect the changes.
- The updates now live are:
- April
- New Tables
plans
(documentation is being updated)
- Columns to Existing Tables
transactions
note
to_operator_name
from_operator_name
to_wallet_vat_number
from_wallet_vat_number
exchange_rate
(can be calculated from currentto_eur
andfrom_eur
conversion rates)
teams
partnerExternalId
type
charge_keys
team_id
user_id
charge_pricing_breakdown
operator_id
subscriptions
serviceConfig
charge_points
partnerExternalId
maxKw
isActive
(Depends on whether state in DWH behaves like the API — a disabled CP might still show an "available" state)costGroupId
sponsorPriceGroupId
sponsorChargePointId
reference
- **
charge_point_sites
**partnerExternalId
- May
- Columns to Existing Tables
transactions
- metadata
- Columns to Existing Tables
- New Tables
2025 - W24
- As promised here the new
future__charges
tables were released today to all partners
2025 - W23
Aircall Calls table released (for specific customers)
Specific customers with custom call center numbers can now analyze their call center activity. This table is manually turned on for customers who request it and who have custom call center numbers in our system
Table documentation for future__charges
(and subtables) now available
future__charges
(and subtables) now availableAs outlines in the 2025+05+28 change log, the update to our charges
table is coming. As promised the documentation is now live for the new future__charges
, future__charges__charge_pricings
and future__charges__charges_config
tables.
2025 - W22
Recent changes to transactions
transactions
(2025-05-28) We recently made 2 changes to the transactions table. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.
- column
transaction_id
is nowid
- columns
to_currency_rate_eur
andfrom_currency_rate_eur
were removed.
Please contact us, if these changes are causing issues in your setup.
Coming changes to charges
table -- June to August 2025
charges
table -- June to August 2025Overview of changes and motivation
(2025-05-28) We are redesigning the way our charges
table is created. This links to deeper re-engineering work at Monta, but also to efforts to make data in the Partner Data Warehouse align more cleanly with the raw data one can query from the API or see in the Hub.
With these changes, we will replace the charges
table and add two new tables charge_pricings
and charges_config
. Some columns currently in charges
will in the future exist in the new tables. The three tables can be joined using charge_id
.
COMING IN WEEK 23: Schema pages for the coming tables
Timing of the changes
- before 2025-06-15: New
charges
,charge_pricings
, andcharges_config
table will appear with theFUTURE__
preposition. No changes will be made to the existing table. - 2025-07-15: Existing
charges
table will be renamed withDEPRECATED__
preposition. New tables will be available both with and without theFUTURE__
preposition allowing preparing your codebase for the future stable state. - 2025-08-15: Tables with the
DEPRECATED__
andFUTURE__
prepositions are dropped
Some highlighted changes in the charges
table
charges
tableis_deleted_charge
column is removed.- This column is always 0 in the current table, so no data is lost
avg_renewable
column is removedstart_source
,payment_method
,payment_method_type
andstate
columns have same universe of values but the values have different format- values are in upper case
- values use
_
separator instead of-
Updated 4 days ago