# ev.energy v2 API The official API for ev.energy, version 2. Version: 2.0 License: Proprietary ## Servers Live API for both production and sandbox requests. ``` https://api.ev.energy/v2 ``` Staging server for internal testing only. ``` https://api-staging.ev.energy/v2 ``` ## Security ### oauth2 Type: oauth2 ## Download OpenAPI description [ev.energy v2 API](https://developers.ev.energy/_bundle/ev.energy-API-v2.yaml) ## Carbon Endpoints for interacting with carbon intensity data. ### List carbon feeds - [GET /carbon_feeds](https://developers.ev.energy/ev.energy-api-v2/carbon/get-carbon_feeds.md): List all carbon feeds visible to the authenticated client. Carbon feeds represent sources of carbon intensity data for specific regions or grids. ### Retrieve a carbon feed - [GET /carbon_feeds/{carbon_feed_id}](https://developers.ev.energy/ev.energy-api-v2/carbon/get-carbon_feeds-carbon_feed_id.md): Retrieve a specific carbon feed, representing a source of carbon intensity data for a region or grid. ### List carbon intensity data - [GET /carbon_feeds/{carbon_feed_id}/carbon_intensities](https://developers.ev.energy/ev.energy-api-v2/carbon/get-carbon_feeds-carbon_feed_id-carbon_intensities.md): Returns a paginated list of carbon intensity data points for a specific carbon feed. Carbon intensity represents the amount of CO2 emissions per unit of electricity generated, measured in grams of CO2 per kilowatt-hour (gCO2/kWh). Use started_at__gte and started_at__lte to filter by time range. ## Charging Sessions Endpoints related to records of charging. ### List charging sub sessions - [GET /charging_sub_sessions](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions.md): List all charging sub sessions visible to the authenticated client. ### Retrieve a charging sub-session - [GET /charging_sub_sessions/{charging_sub_session_id}](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id.md): Retrieve a specific charging sub-session, representing a period of charging in a single mode. ### Retrieve periodic energy usage intervals for a charging sub-session - [GET /charging_sub_sessions/{charging_sub_session_id}/energy_usage](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-energy_usage.md): Retrieve periodic energy usage intervals for a specific charging sub-session. If you are looking for intervals that cover the whole time energy is being delivered (which are therefore of irregular length) use the merge_consecutive_intervals query parameter. ### Retrieve schedules for a charging sub-session - [GET /charging_sub_sessions/{charging_sub_session_id}/schedules](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-schedules.md): Retrieve schedules for a specific charging sub-session. Schedules represent charging instructions for a charging session. Each schedule specifies a current (in milliamps) and a time period during which that current should be applied. ### Retrieve schedule plans for a charging sub-session - [GET /charging_sub_sessions/{charging_sub_session_id}/schedule_plans](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-schedule_plans.md): Retrieve schedule plans for a specific charging sub-session. Schedule plans represent the charging plan parameters used to generate schedules for a charging session. Each plan contains information about the ready-by time, charging requirements, and constraints that were used to create the charging schedule. ### List dispatcher logs - [GET /dispatcher_logs](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-dispatcher_logs.md): List all dispatcher logs for a charging session. These logs record Dispatch Command attempts to EVSEs or Vehicles. ### Charging sub-session created - [POST charging_sub_session.created](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/paths/charging_sub_session.created/post.md): A charging sub-session is created, representing a period of charging in a single mode. ### Charging sub-session ended - [POST charging_sub_session.ended](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/paths/charging_sub_session.ended/post.md): A charging sub-session has ended, representing a period of charging in a single mode. ## EVSEs Endpoints for interacting with EVSEs. ### List EVSEs - [GET /evses](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses.md): List all the EVSEs that the authorization token has access to. ### Retrieve an EVSE - [GET /evses/{evse_id}](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses-evse_id.md): Retrieve a single, specific EVSE's details. ### Decommission an EVSE - [DELETE /evses/{evse_id}](https://developers.ev.energy/ev.energy-api-v2/evses/delete-evses-evse_id.md): Decommission the EVSE by disconnecting it from the ev.energy system. ### List EVSE models - [GET /evse_models](https://developers.ev.energy/ev.energy-api-v2/evses/get-evse_models.md): List all the EVSE models known by the ev.energy system. ### Retrieve an EVSE model - [GET /evse_models/{evse_model_id}](https://developers.ev.energy/ev.energy-api-v2/evses/get-evse_models-evse_model_id.md): Retrieve details for a single, specific EVSE model. ### List EVSE makes - [GET /evse_makes](https://developers.ev.energy/ev.energy-api-v2/evses/get-evse_makes.md): List all the EVSE makes known by the ev.energy system. ### Retrieve an EVSE make - [GET /evse_makes/{evse_make_id}](https://developers.ev.energy/ev.energy-api-v2/evses/get-evse_makes-evse_make_id.md): Retrieve details for a single, specific EVSE make. ### List status logs for an EVSE - [GET /evses/{evse_id}/status_logs](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses-evse_id-status_logs.md): List the historical status logs for a specific EVSE. Used to find out the state of the EVSE at each point it reported in to ev.energy. ### Retrieve a status log for an EVSE - [GET /evses/{evse_id}/status_logs/{sampled_at}](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses-evse_id-status_logs-timestamp.md): An EVSE status log is uniquely identified by the combination of EVSE ID and the time it was sampled at. ### List command logs for an EVSE - [GET /evses/{evse_id}/command_logs](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses-evse_id-command_logs.md): List the historical command logs for a specific EVSE. These logs record commands that were sent to the EVSE. ### Retrieve a command log for an EVSE - [GET /evses/{evse_id}/command_logs/{logged_at}](https://developers.ev.energy/ev.energy-api-v2/evses/get-evses-evse_id-command_logs-timestamp.md): An EVSE command log is uniquely identified by the combination of EVSE ID and the time it was logged at. ### Initiate EVSE onboarding - [GET /evse_onboarding](https://developers.ev.energy/ev.energy-api-v2/evses/get-evse_onboarding.md): Initiate the onboarding process for a new EVSE in your user's browser (or an embedded web view in an app). If neither make_id or model_id are passed as query parameters, the user will be shown a user interface to pick their EVSE make. ## Notifications Endpoints for communicating notifications. ### List notifications - [GET /notifications](https://developers.ev.energy/ev.energy-api-v2/notifications/get-notifications.md): Lists notifications for the user making the request. For each notification it returns a category (INFO, ERROR etc) and a title (in the user's language) for display in their inbox. ### Update a notification - [PATCH /notifications/{notification_id}](https://developers.ev.energy/ev.energy-api-v2/notifications/patch-notifications-notification_id.md): Update a notification. ### Retrieve a notification - [GET /notifications/{notification_id}](https://developers.ev.energy/ev.energy-api-v2/notifications/get-notifications-notification_id.md): Retrieves the full details of a specified notification. The title, short_text and long_text fields will be translated into the user's language. ## Programs Endpoints related to incentivised charging programs. ### List programs - [GET /programs](https://developers.ev.energy/ev.energy-api-v2/programs/get-programs.md): By default, this endpoint returns all programs in our system and does not require authentication. The coordinates, postal_code and country_code query parameters can be used to narrow the list down to just programs eligible for particular locations. Coordinates and postal code searching are mutually exclusive and mixing the query parameters will result in a 400 error response. If the client is authenticated as a specific user (either via Authorisation Code grant type or the EvEnergy-User header) it will return only programs that user is possibly eligible for, based on the location information we have for them. ### Retrieve a program - [GET /programs/{program_id}](https://developers.ev.energy/ev.energy-api-v2/programs/get-programs-program_id.md): Retrieve details for a single, specific program. ### List incentive schemes - [GET /incentive_schemes](https://developers.ev.energy/ev.energy-api-v2/programs/get-incentive_schemes.md): Returns a list of Incentive Schemes that the authenticated User is eligble for. ### Verify user - [POST /programs/{program_id}/user_verification](https://developers.ev.energy/ev.energy-api-v2/programs/post-programs-user-verification.md): Upload a user's utility account information for verification and account matching against the utility's customer data. An endpoint to serve this data will be added in future. ## Rebates Endpoints for interacting with rebates. ### List Rebate Types - [GET /rebate_types](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebate_types.md): Retrieve a list of rebate types available to the user. ### Retrieve rebate type - [GET /rebate_types/{rebate_type_id}](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebate_types-rebate_type_id.md): Retrieve a specific rebate type by id. ### List Rebate Evidence Types - [GET /rebate_evidence_types](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebate_evidence_types.md): Retrieve a list of rebate types available to the user. ### Retrieve rebate evidence type - [GET /rebate_evidence_types/{rebate_evidence_type_id}](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebate_types-rebate_evidence_type_id.md): Retrieve a specific rebate evidence type by id. ### Create rebate application - [POST /user_rebates](https://developers.ev.energy/ev.energy-api-v2/rebates/post-rebates.md): Creates a rebate application, returning the application ID. ### List rebate applications - [GET /user_rebates](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebates.md): Lists all a user's rebate applications. ### Retrieve rebate application - [GET /user_rebates/{user_rebate_id}](https://developers.ev.energy/ev.energy-api-v2/rebates/get-rebates-application_id.md): Retrieve a specific rebate application. ### Update rebate application - [PATCH /user_rebates/{user_rebate_id}](https://developers.ev.energy/ev.energy-api-v2/rebates/patch-user_rebates-application_id.md): Attach evidence to a rebate application. ### Submit a completed rebate form - [POST /user_rebates/{user_rebate_id}:submit](https://developers.ev.energy/ev.energy-api-v2/rebates/post-user_rebates-application_id-:submit.md): Once all evidence data and files have been uploaded, this endpoint is called to submit the rebate application for review by updating the Form status to "complete" and the application status to "pending_review". ### Start a file upload - [POST /rebate_evidence_files:start_upload](https://developers.ev.energy/ev.energy-api-v2/rebates/post-rebate-evidence_files:start_upload.md): This endpoint creates the RebateEvidenceFile record and returns its uid as well as a presigned URL to use for direct upload to AWS S3. ### Finalize File Upload - [POST /rebate_evidence_files/{rebate_evidence_file_id}:finish_upload](https://developers.ev.energy/ev.energy-api-v2/rebates/post-rebate-evidence_files-evidence_file_id-:finish_upload.md): After the file is successfully uploaded to S3 via the presigned URL, this endpoint is called to set the upload_finished_at timestamp on the evidence_file record. ### List rebate evidence files - [GET /rebate_evidence_files](https://developers.ev.energy/ev.energy-api-v2/rebates/get-user_rebates-application_id-evidence_files.md): List all user's rebate evidence files ### Retrieve rebate evidence file details - [GET /rebate_evidence_files/{rebate_evidence_file_id}](https://developers.ev.energy/ev.energy-api-v2/rebates/get-user_rebates-application_id-evidence_files-evidence_file_id.md): Retrieve the details of a specific rebate evidence file. ## Root The root endpoint which lists all the top-level collections. ### API root - [GET /](https://developers.ev.energy/ev.energy-api-v2/root/get-root.md): Get links to resources accessible in the API. ## Sites Endpoints for interacting with sites containing multiple EVSEs. ### List EVSE Sites - [GET /evse_sites](https://developers.ev.energy/ev.energy-api-v2/sites/get-evse_sites.md): List all available EVSE Sites ### Retrieve an EVSE Site - [GET /evse_sites/{evse_site_id}](https://developers.ev.energy/ev.energy-api-v2/sites/get-evse_sites-evse_site_id.md): Retrieve a single, specific EVSESite's details. ### List CPMS Providers - [GET /cpms_providers](https://developers.ev.energy/ev.energy-api-v2/sites/get-cpms_providers.md): Get a list of all the ChargePoint Management System Providers that we integrate with. ### Retrieve a CPMS Provider - [GET /cpms_providers/{cpms_provider_id}](https://developers.ev.energy/ev.energy-api-v2/sites/get-cpms_providers-provider_id.md): Get details on a single CPMS provider. ## Solar Endpoints for interacting with solar arrays and inverters. ### List solar arrays - [GET /solar_arrays](https://developers.ev.energy/ev.energy-api-v2/solar/get-solar-arrays.md): List all the solar arrays that the authorization token has access to. ### Create a solar array - [POST /solar_arrays](https://developers.ev.energy/ev.energy-api-v2/solar/post-solar-arrays.md): Creates a solar array and associates it with the user. ### Retrieve a solar array - [GET /solar_arrays/{solar_array_id}](https://developers.ev.energy/ev.energy-api-v2/solar/get-solar-arrays-solar_array_id.md): Retrieve a single, specific solar array's details. ### Update a solar array - [PATCH /solar_arrays/{solar_array_id}](https://developers.ev.energy/ev.energy-api-v2/solar/patch-solar_arrays-solar_array_id.md): Update a solar array. ### Create an Inverter - [POST /inverters](https://developers.ev.energy/ev.energy-api-v2/solar/post-inverters.md): Creates an Inverter and associates it with a user's solar array. ### List inverters - [GET /inverters](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverters.md): List all the inverters that the authorization token has access to. ### Retrieve an inverter - [GET /inverters/{inverter_id}](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverters-inverter_id.md): Retrieve a single, specific inverter's details. ### List inverter makes - [GET /inverter_makes](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverter_makes.md): List all the inverter makes known by the ev.energy system. ### Retrieve an inverter make - [GET /inverter_makes/{inverter_make_id}](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverter_makes-inverter_make_id.md): Retrieve details for a single, specific EVSE make. ### List inverter models - [GET /inverter_models](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverter_models.md): List all the inverter models known by the ev.energy system. ### Retrieve an inverter model - [GET /inverter_models/{inverter_model_id}](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverter_models-inverter_model_id.md): Retrieve details for a single, specific inverter model. ### Allows a user to authenticate with their inverter account. - [GET /inverter_onboarding](https://developers.ev.energy/ev.energy-api-v2/solar/get-inverter_onboarding.md): This endpoint will redirect to a web page that a user can use to login into their inverter account. This should be visited in a web browser as it contains interactive UI elements. ## Subscriptions Endpoints for interacting with user subscriptions. ### List subscriptions - [GET /subscriptions](https://developers.ev.energy/ev.energy-api-v2/subscriptions/get-subscriptions.md): List all the valid subscriptions that the authorization token has access to. ### Retrieve a subscription offering - [GET /subscription_offerings/{offering_id}](https://developers.ev.energy/ev.energy-api-v2/subscriptions/get-subscription-offerings-offering_id.md): Retrieve a single, specific subscription offering's details. ## Support Tickets Endpoints for interacting with customer support tickets. ### List support tickets - [GET /support_tickets](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_tickets.md): List all support tickets that the authorization token has access to. Access control: - User-scoped tokens: Returns only tickets belonging to that user - Organization-scoped tokens: Returns only tickets belonging to users in that organization - Tokens with access_all_areas: Returns all tickets including those without a user Note: Tickets without a user (null user field) are only accessible to applications with access_all_areas permission. These tickets represent inquiries from channels where a user account may not exist (e.g., pre-signup inquiries, web forms). ### Retrieve support ticket - [GET /support_tickets/{support_ticket_id}](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_tickets-support_ticket_id.md): Retrieve information about a single, specific support ticket. Access control: - User-scoped tokens: Can only access tickets belonging to that user - Organization-scoped tokens: Can only access tickets belonging to users in that organization - Tokens with access_all_areas: Can access all tickets including those without a user Note: Tickets without a user (null user field) will return 404 for tokens without access_all_areas permission. ### Update support ticket - [PATCH /support_tickets/{support_ticket_id}](https://developers.ev.energy/ev.energy-api-v2/support-tickets/patch-support_tickets-support_ticket_id.md): Update support ticket categorization. Access control follows the same rules as retrieval: - User-scoped tokens: Can only update tickets belonging to that user - Organization-scoped tokens: Can only update tickets belonging to users in that organization - Tokens with access_all_areas: Can update all tickets including those without a user ### Get support ticket categories - [GET /support_tickets/categories](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_tickets-categories.md): Returns all available support ticket categories and subcategories. ### Get support ticket Sankey diagram data - [GET /support-ticket-stats/sankey](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-sankey.md): Returns aggregated data for visualizing ticket flow from category to subcategory in a Sankey diagram. Only includes tickets with human-verified categories. ### Get support ticket volume time series - [GET /support-ticket-stats/volume](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-volume.md): Returns time series data showing ticket volume over time. Can be grouped by day, week, or month. ### Get support ticket resolution metrics - [GET /support-ticket-stats/resolution](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-resolution.md): Returns metrics about ticket resolution including resolution rate, average and median resolution times. ### Get support ticket status breakdown - [GET /support-ticket-stats/status](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-status.md): Returns the distribution of tickets across different status values. ### Get support ticket priority breakdown - [GET /support-ticket-stats/priority](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-priority.md): Returns the distribution of tickets across different priority values. ### Get support ticket source breakdown - [GET /support-ticket-stats/source](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-source.md): Returns the distribution of tickets across different source values. ### Get top support ticket categories and subcategories - [GET /support-ticket-stats/top-categories](https://developers.ev.energy/ev.energy-api-v2/support-tickets/get-support_ticket_stats-top-categories.md): Returns the most common categories and subcategories sorted by ticket count. Supports a limit parameter to control the number of results. ## Tariffs Endpoints related to energy suppliers and their tariffs. ### List suppliers, sorted alphabetically by name. - [GET /suppliers](https://developers.ev.energy/ev.energy-api-v2/tariffs/get-suppliers.md): List all the energy suppliers known by the ev.energy system. Use the available_for_user_id query parameter to narrow the list to only those relevant to a specific user. ### Retrieve a supplier - [GET /suppliers/{supplier_id}](https://developers.ev.energy/ev.energy-api-v2/tariffs/get-suppliers-suppler_id.md): Retrieve details for a single, specific energy supplier. ### List tariffs, sorted alphabetically by name. - [GET /tariffs](https://developers.ev.energy/ev.energy-api-v2/tariffs/get-tariffs.md): List all the energy supplier tariffs known by the ev.energy system. Use the available_for_user_id query parameter to narrow the list to only those relevant to a specific user and supplier query parameter to list only tariffs for a specific supplier. ### Retrieve a tariff - [GET /tariffs/{tariff_id}](https://developers.ev.energy/ev.energy-api-v2/tariffs/get-tariffs-tariff_id.md): Retrieve details for a single, specific tariff. ### List prices for a tariff - [GET /tariffs/{tariff_id}/prices](https://developers.ev.energy/ev.energy-api-v2/tariffs/get-tariff-prices.md): Returns all prices for the specified tariff. Results are ordered by start time (most recent first). Use started_at__gte and started_at__lte to filter by time range. ## Users Endpoints for interacting with users. ### List users - [GET /users](https://developers.ev.energy/ev.energy-api-v2/users/get-users.md): List all the users that the authorization token has access to. ### Create user - [POST /users](https://developers.ev.energy/ev.energy-api-v2/users/post-users.md): Create an individual user in the ev.energy system. ### Retrieve user - [GET /users/{user_id}](https://developers.ev.energy/ev.energy-api-v2/users/get-users-user_id.md): Retrieve information about a single, specific user. ### Update User - [PATCH /users/{user_id}](https://developers.ev.energy/ev.energy-api-v2/users/patch-users-user_id.md): Update user information. ## Vehicles Endpoints for interacting with vehicles. ### List vehicles - [GET /vehicles](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles.md): List all the vehicles that the authorization token has access to. ### Create unintegrated vehicle - [POST /vehicles](https://developers.ev.energy/ev.energy-api-v2/vehicles/post-vehicles.md): If a vehicle cannot be integrated with our system, an "unintegrated" vehicle must be created instead to represent it and record important details like battery size. To add a vehicle that can be integrated, see the Onboarding documentation. ### Retrieve a vehicle - [GET /vehicles/{vehicle_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id.md): Retrieve a single, specific vehicle's details. ### Update a vehicle - [PATCH /vehicles/{vehicle_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/patch-vehicles.md): Update a vehicle. ### Remove a vehicle - [DELETE /vehicles/{vehicle_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/delete-vehicles.md): Remove a vehicle by disconnecting it from the ev.energy system. ### List vehicle trims - [GET /vehicle_trims](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_trims.md): List all the vehicle trims known by the ev.energy system. Trim refers to a set of features that can be applied to a particular model of vehicle: https://en.wikipedia.org/wiki/Car_model#Trim_level. ### Create a custom vehicle trim - [POST /vehicle_trims](https://developers.ev.energy/ev.energy-api-v2/vehicles/post-vehicle_trims.md): Creates a new trim for the specified model that can be used if we are missing a trim. These trims will not be available in the list trims api call ### Retrieve a vehicle trim - [GET /vehicle_trims/{vehicle_trim_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_trims-vehicle_trim_id.md): Retrieve details for a single, specific vehicle trim. Trim refers to a set of features that can be applied to a particular model of vehicle: https://en.wikipedia.org/wiki/Car_model#Trim_level. ### List vehicle models - [GET /vehicle_models](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_models.md): List all the vehicle models known by the ev.energy system. ### Create vehicle model - [POST /vehicle_models](https://developers.ev.energy/ev.energy-api-v2/vehicles/post-vehicle_models.md): Create a new vehicle model in the ev.energy system. Newly created models are hidden by default and must be reviewed before becoming visible. ### Retrieve a vehicle model - [GET /vehicle_models/{vehicle_model_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_models-vehicle_model_id.md): Retrieve details for a single, specific vehicle model. ### List vehicle makes - [GET /vehicle_makes](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_makes.md): List all the vehicle makes known by the ev.energy system. ### Retrieve a vehicle make - [GET /vehicle_makes/{vehicle_make_id}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_makes-vehicle_make_id.md): Retrieve details for a single, specific vehicle make. ### List status logs for a vehicle - [GET /vehicles/{vehicle_id}/status_logs](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-status_logs.md): List the historical status logs for a specific Vehicle. Used to find out the state of the Vehicle at each point it reported in to ev.energy. ### Retrieve a specific status log for a vehicle - [GET /vehicles/{vehicle_id}/status_logs/{sampled_at}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-status_logs-timestamp.md): A single status log for a particular vehicle is uniquely identified by the timestamp it was logged at. ### List API error logs for a vehicle - [GET /vehicles/{vehicle_id}/error_logs](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-error_logs.md): List the historical API error logs for a specific Vehicle. These logs capture errors that occurred when attempting to communicate with the vehicle's telematics API. ### Retrieve a specific API error log for a vehicle - [GET /vehicles/{vehicle_id}/error_logs/{logged_at}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-error_logs-timestamp.md): A single API error log for a particular vehicle is uniquely identified by the timestamp it was logged at. ### List location logs for a vehicle - [GET /vehicles/{vehicle_id}/location_logs](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-location_logs.md): List the historical location log timestamps for a specific Vehicle. Returns metadata about when location data was recorded, without exposing the actual location coordinates. ### Retrieve a specific location log for a vehicle - [GET /vehicles/{vehicle_id}/location_logs/{sampled_at}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-location_logs-timestamp.md): A single location log for a particular vehicle is uniquely identified by the timestamp it was sampled at. Returns metadata only, without exposing the actual location coordinates. ### List command logs for a vehicle - [GET /vehicles/{vehicle_id}/command_logs](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-command_logs.md): List the historical command logs for a specific Vehicle. These logs record commands that were sent to the vehicle. ### Retrieve a specific command log for a vehicle - [GET /vehicles/{vehicle_id}/command_logs/{logged_at}](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicles-vehicle_id-command_logs-timestamp.md): A single command log for a particular vehicle is uniquely identified by the timestamp it was logged at. ### Initiate vehicle onboarding - [GET /vehicle_onboarding](https://developers.ev.energy/ev.energy-api-v2/vehicles/get-vehicle_onboarding.md): Initiate the onboarding process for a new vehicle in your user's browser (or an embedded web view in an app). If none of make_id, model_id or trim_id are passed as query parameters, the user will be shown a user interface to pick their vehicle make. ### Create reconnection URL - [POST /vehicles/{vehicle_id}/reconnect](https://developers.ev.energy/ev.energy-api-v2/vehicles/post-vehicles-vehicle_id-reconnect.md): Create a reconnection request URL for the Vehicle. ## Webhooks Endpoints for configuring and managing webhooks. ### Retrieve access link for webhook portal - [GET /webhook_portal](https://developers.ev.energy/ev.energy-api-v2/webhooks/get-webhook_portal.md): Generate a one time use link to access the portal to configure webhooks.