Charge Key Authorizations (Charge Point Owner)

One row per charge-key authorization attempt (an RFID/vehicle-ID tap or a roaming request) on
charge points you own — every attempt on your network, including keys you don't manage (a
partner's or an unknown driver's token). The presented key's identity and the detailed reason for
the outcome are only included when you also own the key; otherwise those columns are empty.

If you also own the key used, see
Charge Key Authorizations (Key Owner) for that side of
the data.

SQL: charge_key_authorizations_charge_point_owner

Schema

Column Name	Data Type	Description
Primary ID
authorization_id	INTEGER	Primary key of the authorization attempt
Other IDs
duplicate_of_auth_id	INTEGER	The canonical authorization this row duplicates; empty when this row is the real event
charge_key_id	INTEGER	Always empty in this table — you only see the key's identity when you own it too, via `charge_key_authorizations_key_owner`
charge_key_operator_id	INTEGER	Always empty in this table
charge_key_parent_operator_id	INTEGER	Always empty in this table
charge_key_team_id	INTEGER	Always empty in this table
charge_key_user_id	INTEGER	Always empty in this table (a direct link to a driver's personal account)
charge_point_id	INTEGER	The charge point the attempt was made on
charge_point_integration_id	INTEGER	Integration identifier of the charge point
charge_point_operator_id	INTEGER	Operator that owned the charge point at the time of the attempt
charge_point_parent_operator_id	INTEGER	Parent operator of charge_point_operator_id, if any
charge_point_team_id	INTEGER	Team that owned the charge point at the time of the attempt
ocpi_operator_id	INTEGER	OCPI counterparty operator id, if the attempt was a roaming request
hubject_operator_id	INTEGER	Hubject counterparty operator id, if the attempt was routed through Hubject
charge_id	INTEGER	The resulting charge, if the authorization led to one
request_id	VARCHAR	Identifier of the originating request
Timestamps
occurred_at	TIMESTAMP_NTZ	When the authorization attempt occurred
created_at	TIMESTAMP_NTZ	When the record was created
updated_at	TIMESTAMP_NTZ	When the record was last updated
Filters
is_duplicate	BOOLEAN	True when this row is a fan-out duplicate (duplicate_of_auth_id is not empty)
Attributes
charge_key_name	VARCHAR	Always empty in this table
charge_point_name	VARCHAR	Display name of the charge point
charge_point_operator_name	VARCHAR	Name of the operator that owned the charge point
charge_point_address1	VARCHAR	Charge point street address
charge_point_city	VARCHAR	Charge point city
charge_point_zip	VARCHAR	Charge point postal code
charge_point_visibility	VARCHAR	Charge point visibility setting (e.g. public/private)
result	VARCHAR	Outcome of the authorization attempt (e.g. allowed, denied, error)
reason	VARCHAR	Always empty in this table — the detailed reason is only visible to the key's owner
raw_reason_code	VARCHAR	Always empty in this table
reason_vocabulary	VARCHAR	Always empty in this table
attempts	INTEGER	Number of attempts recorded for this authorization event
token_identifier	VARCHAR	Always empty in this table — a charge point owner does not own the key, so only the last 4 characters are shown, to avoid exposing full credentials for keys you don't manage
token_identifier_last4	VARCHAR	Last 4 characters of the token identifier; empty if the token is too short or absent
channel	VARCHAR	Channel the authorization request came through
source	VARCHAR	Source system of the authorization event
direction	VARCHAR	Inbound (own EVSE) or outbound (roaming out) direction of the request
partner_country_code	VARCHAR	Country code of the roaming partner, if applicable
partner_party_id	VARCHAR	OCPI party id of the roaming partner, if applicable
location_id	VARCHAR	OCPI location id of the charge point
evse_uid	VARCHAR	EVSE identifier the attempt targeted
connector_id	VARCHAR	Connector identifier the attempt targeted
session_reference	VARCHAR	External session reference, if any
authorizer	VARCHAR	System/actor that authorized the attempt
message	VARCHAR	Always empty in this table — may otherwise include a driver's financial-state detail, visible only to the key's owner

Data inclusion criteria

You (or a team under your parent operator) own the charge point the attempt was made on

Data flow

Upstream tables	Downstream tables
`charge_keys`	---
`charge_points`