# AMPECO EV Charging Platform Documentation

> The official Developer Hub of the AMPECO EV charging platform

Append .md to any documentation page URL to get its markdown version.

## Guides
- [Overview of the platform](https://developers.ampeco.com/docs/overview.md)
- [API functional components](https://developers.ampeco.com/docs/main-players.md)
- [Models relationship](https://developers.ampeco.com/docs/models-relationship.md)
- [Initial Sign Up in Driver App](https://developers.ampeco.com/docs/initial-sign-up-in-driver-app.md): An EV driver uses the mobile app to register for the charging service.
- [Login to the Driver App](https://developers.ampeco.com/docs/login-to-the-driver-app.md): Describes the login process into the mobile driver app
- [Start a Charging Session](https://developers.ampeco.com/docs/start-a-charging-session.md): EV driver starts a charging session via a mobile app and monitors the session's progress in real time.
- [Stop a Charging Session](https://developers.ampeco.com/docs/stop-a-charging-session.md): EV driver stops a charging session via the mobile app and sees a recap of charging data.
- [Select a Charge Point Connector on a Map in the Driver App](https://developers.ampeco.com/docs/select-a-charge-point-connector-on-a-map-in-the-driver-app.md): EV Driver locates and selects a charge point connector on a map in the mobile app.
- [Set Charging Profile During a Transaction](https://developers.ampeco.com/docs/set-charging-profile-during-a-transaction.md): Configuring a Custom Charging Profile During an Active Transaction
- [Save EV MAC Address for Autocharge](https://developers.ampeco.com/docs/save-ev-mac-address-for-autocharge.md): Save EV MAC Address Without Manual Entry for Autocharge Purposes
- [Save EV MAC Address For Autocharge With User Consent](https://developers.ampeco.com/docs/save-ev-mac-address-for-autocharge-with-user-consent.md): Saving an EV MAC Address to Enable Autocharge
- [Create a New Circuit](https://developers.ampeco.com/docs/create-a-new-circuit.md): Create a new circuit with specific attributes - number of phases, max current, charge points details.
- [Delete a Circuit](https://developers.ampeco.com/docs/delete-a-circuit.md): Deleting a circuit configuration via API
- [View Available Circuits](https://developers.ampeco.com/docs/view-available-circuits.md): Display available configurations of electrical circuits.
- [Read Circuit](https://developers.ampeco.com/docs/read-circuit.md): User Views Detailed Configuration of a Selected Circuit
- [Update Existing Circuit](https://developers.ampeco.com/docs/update-existing-circuit.md): Navigate through the circuit configuration update process in the API
- [Show Consumption Of a Single Phase In an Electrical Circuit](https://developers.ampeco.com/docs/show-consumption-of-a-single-phase-in-an-electrical-circuit.md): Monitoring consumption of a specific phase in a circuit via API
- [Show Consumption Of All Circuit Phases](https://developers.ampeco.com/docs/show-consumption-of-all-circuit-phases.md): Retrieve and monitor latest consumption data of a circuit.
- [Reserve a Charge Point](https://developers.ampeco.com/docs/reserve-a-charge-point.md): Making a Reservation of a Specific Charge Point
- [Reserve a Charge Point for a Specific Time in the Future](https://developers.ampeco.com/docs/reserve-a-charge-point-for-a-specific-time-in-the-future.md): Make a Reservation of a Charge Point in Advance for a Given Time
- [Available Personal Smart Charging Modes](https://developers.ampeco.com/docs/smart-charging-setup-for-home-chargers.md): Which modes are active for my home charger?
- [Set Personal Smart Charging Preferences](https://developers.ampeco.com/docs/set-smart-charging-preferences.md): Create or Update Personal (Home) Smart Charging Preferences
- [Fetch currently applied Smart Charging Preferences](https://developers.ampeco.com/docs/fetch-currently-applied-smart-charging-preferences.md): Check the current status of the Smart Charging capability applied to user's home charger
- [Setup Smart Charging (Public, Private, Personal/Home)](https://developers.ampeco.com/docs/setup-smart-charging-public-private-personalhome.md): Configure the Smart Charging settings
- [User Controlled Schedule Flow](https://developers.ampeco.com/docs/user-controlled-schedule-flow.md): Here is a detailed suggestion on how to implement the *user_controlled_schedule* flow for your own app
- [Download Receipts in the Driver App](https://developers.ampeco.com/docs/download-receipts-in-the-driver-app.md): EV Driver reviews and downloads receipts in the Driver App for a certain time period
- [Activate a New Subscription](https://developers.ampeco.com/docs/activate-a-new-subscription.md): Choose a subscription plan to an EV charging service from a list of available options.
- [Cancel an Active Subscription](https://developers.ampeco.com/docs/cancel-an-active-subscription.md): User cancels an active subscription via the application
- [Redeem a Voucher](https://developers.ampeco.com/docs/redeem-a-voucher.md): EV driver redeems a voucher by entering a voucher code.
- [Migrate Existing Users](https://developers.ampeco.com/docs/migrate-existing-users.md): Overview of steps related to migrating existing users to our charge point management system.
- [Creating custom widgets in the back office](https://developers.ampeco.com/docs/creating-custom-widgets-in-the-back-office.md)
- [Creating custom dashboards in the back office](https://developers.ampeco.com/docs/creating-custom-dashboards-in-the-back-office.md)
- [Adding widgets to resource pages in the back office](https://developers.ampeco.com/docs/adding-widgets-to-resource-pages-in-the-back-office.md)

## API Reference
- [Authorization](https://developers.ampeco.com/reference/authorization-1.md)
- [Pagination](https://developers.ampeco.com/reference/pagination.md)
- [Notifications](https://developers.ampeco.com/reference/notifications-1.md)
- [Data formats](https://developers.ampeco.com/reference/data-formats.md)
- [EVSE statuses](https://developers.ampeco.com/reference/evse-statuses.md)
- [Backward compatibility](https://developers.ampeco.com/reference/backward-compatibility.md)
- [API rate limits](https://developers.ampeco.com/reference/limits.md)
- [API AI skill](https://developers.ampeco.com/reference/api-ai-skill.md): Use natural language to discover endpoints, schemas, and integration patterns
- [Certificate / Reissue an EMAID](https://developers.ampeco.com/reference/certificatereissueanemaid.md)
- [Certificate / Issue an EMAID](https://developers.ampeco.com/reference/certificateissueanemaid.md)
- [Charge Point / Change Availability](https://developers.ampeco.com/reference/chargepointchangeavailability.md): change the availability to available or unavailable. A Charge Point is considered unavailable when it does not allow any charging.
- [Charge Point / Change Owner](https://developers.ampeco.com/reference/chargepointchangeowner.md): Change the owner of the Charge Point
- [Charge Point / Check Tariff Display Support](https://developers.ampeco.com/reference/chargepointchecktariffdisplaysupport.md): Sends a DataTransfer probe to check whether the charge point supports tariff and cost display messages. If supported, the feature can be enabled automatically based on the request parameter.  This action is only available for OCPP 1.6 charge points that do not have the CustomDisplayCostAndPrice configuration key set to true, and are not roaming or demo charge points.
- [Charge Point / Clear cache](https://developers.ampeco.com/reference/chargepointclearcache.md): Clear cache of a charge point
- [Charge Point / Clear Charging Profile](https://developers.ampeco.com/reference/chargepointclearchargingprofile.md): If you are not using networkId and not passing other criteria in the body it will clear the charging profile for the charge point (ChargePointMaxProfile). If you are using evse_network_id you will clear the charging profile just for that evse (TxDefaultProfile)
- [Charge Point / Disconnect](https://developers.ampeco.com/reference/chargepointdisconnect.md): Disconnect a charge point
- [Charge Point / Get Composite Schedule](https://developers.ampeco.com/reference/chargepointgetcompositeschedule.md): Request the composite charging schedule from a charge point. When evseNetworkId is omitted, returns the combined schedule at grid connection level (connectorId=0).
- [Charge Point / Get Diagnostics](https://developers.ampeco.com/reference/chargepointgetdiagnostics.md): Request a get diagnostics upload from the charge point
- [Charge Point / Get Local List Version](https://developers.ampeco.com/reference/chargepointgetlocallistversion.md): Request the current version number of the local authorization list from a charge point.
- [Charge Point / Get Security Log](https://developers.ampeco.com/reference/chargepointgetsecuritylog.md)
- [Charge Point / Move EVSEs to Satellite](https://developers.ampeco.com/reference/chargepointmoveevsestosatellite.md): Move one or more EVSEs from this charge point to a satellite charge point
- [Charge Point / Reserve](https://developers.ampeco.com/reference/chargepointreserve.md): Reserve an evse
- [Charge Point / Reset Security Profile](https://developers.ampeco.com/reference/chargepointresetsecurityprofile.md): Reset the current security profile of the charge point in the backend. The next time the charge point connects, the backend will accept the connection and update the current security profile with the one that the charge point actually used to establish the connection
- [Charge Point / Reset](https://developers.ampeco.com/reference/chargepointreset.md): Reset a charge point
- [Charge Point / Send Custom OCPP Command](https://developers.ampeco.com/reference/chargepointsendcustomocpp.md): Send a custom OCPP message to a charge point. This is a synchronous endpoint that waits for the charge point response or timeout. The raw response from the charge point is returned without transformation.
- [Charge Point / Send Data Transfer](https://developers.ampeco.com/reference/chargepointsenddatatransfer.md)
- [Charge Point / Set Charging Profile](https://developers.ampeco.com/reference/chargepointsetchargingprofile.md): Set a smart charging profile
- [Charge Point / Start Charging Session Without EVSE](https://developers.ampeco.com/reference/chargepointstartchargingsessionwithoutevse.md): Start a charging session
- [Charge Point / Start Charging Session](https://developers.ampeco.com/reference/chargepointstartchargingsession.md): Start a charging session
- [Charge Point / Stop Charging Session](https://developers.ampeco.com/reference/chargepointstopchargingsession.md): Stop a charging session
- [Charge point / Sync configuration](https://developers.ampeco.com/reference/chargepointsyncconfiguration.md): Send a partial or full sync configuration request to the charge point. The response includes a requestId that you can monitor using the ChargePointSyncConfigurationNotification. Please note that calling this action should not be required, as each time the charge point boots the configuration is automatically synced. Under normal conditions it should be impossible for a configuration key to change at runtime without the central systems request.
- [Charge Point / Trigger Message Charge Point](https://developers.ampeco.com/reference/chargepointtriggermessagechargepoint.md): Trigger message to given Charge Point
- [Charge Point / EVSE / Unlock](https://developers.ampeco.com/reference/chargepointevseunlock.md): Unlock an EVSE
- [Charge Point / Change sharing code](https://developers.ampeco.com/reference/chargepointchangesharingcode.md): Change sharing code for the Charge Point
- [Charge Point / Delete Certificate](https://developers.ampeco.com/reference/chargepointdeletecertificate.md): Delete certificate
- [Charge Point / Install Certificate](https://developers.ampeco.com/reference/chargepointinstallcertificate.md)
- [Charge Point / Set Configuration](https://developers.ampeco.com/reference/chargepointsetconfiguration.md): Set Configuration for the Charge Point
- [Charge Point / Set Security Profile](https://developers.ampeco.com/reference/chargepointsetsecurityprofile.md): Set the security profile of the charge point. This operation installs Amazon root certificates (RSA & EC) and attempts to raise the security profile to the specified level. Only allows raising the profile (transitions 0→1, 0→2, 1→2), not lowering it.
- [Charge Point / Get Installed Certificate IDs](https://developers.ampeco.com/reference/chargepointgetinstalledcertificateids.md)
- [Charge Point / Update Firmware](https://developers.ampeco.com/reference/chargepointupdatefirmware.md)
- [Circuit / Attach Charge Point](https://developers.ampeco.com/reference/circuitattachchargepoint.md): To maintain safety and compatibility, only charge points with an identical electrical configuration to the circuit can be added.
- [Circuit / Detach Charge Point](https://developers.ampeco.com/reference/circuitdetachchargepoint.md)
- [Circuit / Set Charge Point Priority](https://developers.ampeco.com/reference/circuitsetchargepointpriority.md)
- [Circuit / Set Charge Point EVSE Priority](https://developers.ampeco.com/reference/circuitsetchargepointevsepriority.md)
- [Circuit / Set Circuit SoC Priority](https://developers.ampeco.com/reference/circuitsetcircuitsocpriority.md): Set DLM priority based on the session's state of charge (SoC). The active priority will be used to either decrease or increase the energy used by the session's EVSE. - If the SoC exceeds the `upperThresholdPercent`, then the `highSoCPriority` will be applied. - If the SoC is below the `lowerThresholdPercent`, then the `lowSoCPriority` will be applied. - If neither of the above conditions is true, then the priority is set to 1.  You can provide either the `upperThresholdPercent` with the `highSoCPriority` or the `lowerThresholdPercent` with the `lowSoCPriority` or both pairs. When a lower or upper threshold is not set, the default priority of 1 will be used.
- [Circuit / Set Session Boost](https://developers.ampeco.com/reference/circuitsetsessionboost.md): Sets the per-session DLM boost flag for an active session.  When enabled, the boosted EVSE receives the unused headroom between the active circuit constraint (schedule limit and/or flexibility request) and the circuit's maximum capacity, capped at the EVSE's maximum supported current. The change applies on the next DLM algorithm tick.  The flag persists for the remainder of the session. The boost ends when either the session ends (no explicit call required) or the client sends this action again with `enabled: false`.  Sending the same value the session already carries is accepted as an idempotent no-op (returns 202 with no second effect).  The action is rejected with HTTP 422 if the session is not in the active state.
- [Circuit / Set Session Priority](https://developers.ampeco.com/reference/circuitsetsessionpriority.md)
- [Configuration Template / Apply to Charge Points](https://developers.ampeco.com/reference/configurationtemplateapplytochargepoints.md): Apply a configuration template to charge points.
- [Configuration Template / Bulk Create Variables](https://developers.ampeco.com/reference/configurationtemplatebulkcreatevariables.md): Create multiple variables for a specific configuration template, adds them to the already existing keys and validates if there are duplicates.
- [Electricity Meter / Report Consumption](https://developers.ampeco.com/reference/electricitymeterreportconsumption.md): Add an electricity meter report for the meter readings at the current moment
- [Energy coupon / Redeem code](https://developers.ampeco.com/reference/energycouponredeemcode.md): Redeem a coupon or template code for a specific user.
- [Energy coupon / Cancel](https://developers.ampeco.com/reference/energycouponcancel.md): Permanently cancels an energy coupon, setting its status to `cancelled`. Any remaining energy on the coupon is forfeited and can no longer be used for charging sessions. Coupons that are currently locked (actively being used in a charging session) cannot be cancelled.
- [Energy coupon template / Deactivate](https://developers.ampeco.com/reference/energycoupontemplatedeactivate.md): Deactivate an energy coupon template by setting its status to expired. No new redemptions will be possible. Existing coupons are not affected.  Only templates with status active, paused or expired can be deactivated.
- [EVSEs / Bulk Assign Tariff Groups](https://developers.ampeco.com/reference/evsebulkassigntariffgroups.md): Bulk assign tariff groups for multiple EVSEs. This action allows you to assign or unassign tariff groups to multiple EVSEs at once, filtered by location, partner, evses and tariff groups.  The update is processed synchronously and there is a limit of max 1000 EVSEs per request.
- [EVSE / Start Charging with EVSE ID](https://developers.ampeco.com/reference/evsestartchargingwithevseid.md): Start a charging session
- [EVSE / Trigger Message](https://developers.ampeco.com/reference/evsetriggermessage.md): Trigger message to given EVSE
- [Flexibility Asset / Change Status](https://developers.ampeco.com/reference/changeflexibilityassetstatus.md): Change the status of the Flexibility Asset
- [Flexibility Asset / Create Activation Request](https://developers.ampeco.com/reference/flexibilityassetcreateactivationrequest.md): Create Flexibility Activation Request for a specific Asset
- [Actions / Assign Charge Points](https://developers.ampeco.com/reference/assigninstallerjobchargepoints.md): Assign charge points to an installer job
- [Actions / Change Status](https://developers.ampeco.com/reference/changeinstallerjobstatus.md): Change the status of an installer job
- [Invoice / Update External ID](https://developers.ampeco.com/reference/invoiceupdateexternalid.md): Update the external ID reference for an invoice. This allows linking the invoice to an external accounting or ERP system.
- [Location / Check Booking Availability](https://developers.ampeco.com/reference/locationcheckbookingavailability.md): Get a consolidated view of EVSEs availability for a given location and time frame. Returns available time slots for each bookable EVSE at the location.
- [Notifications / Resend Failed](https://developers.ampeco.com/reference/notificationsresendfailed.md): Resend failed webhook notifications.  - Resend for a specific notification ID can be requested once every 15 minutes. - Notifications that are disabled cannot be resent. - Each failed notification will be resent only once. If it fails again, it will be added back to the failed notifications list.
- [Parking Space / Update occupancy status](https://developers.ampeco.com/reference/parkingspaceupdateoccupancystatus.md)
- [Partner invite corporate billing policy / Disable](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicydisable.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Disable a partner invite corporate billing policy.
- [Partner invite corporate billing policy / Enable](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicyenable.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Enable a partner invite corporate billing policy.
- [Partner invoice / Issue credit note](https://developers.ampeco.com/reference/partnerinvoiceissuecreditnote.md): Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, is marked paid, and references the cancelled invoice via `referenceId`. Only invoices generated through the built-in B2B invoice integration are eligible, and only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported.  A `409` means the invoice is permanently ineligible and the request will not succeed on retry. It is returned when the invoice already has a credit note, when the target is itself a credit note, or when the invoice was not generated through the built-in B2B invoice integration.
- [Partner invoice / Update external ID](https://developers.ampeco.com/reference/partnerinvoiceupdateexternalid.md): Update or clear the external invoice reference ID for a partner invoice. Used for integration with external accounting systems.
- [Partner settlement report / Issue partner invoice](https://developers.ampeco.com/reference/partnersettlementreportissuepartnerinvoice.md): This action validates the given settlement report and accepts it for partner invoice generation. The settlement report must have a B2B invoice processor configured on its operator and must not already have been invoiced. Both balance directions are eligible. When expenses are greater than or equal to revenue, the action produces a regular partner invoice on which the operator is the seller. When expenses are lower than revenue, the balance is in the partner's favor and the action produces a self-billing invoice on which the partner is the seller.  Invoice generation runs asynchronously after the request is accepted; the `202` confirms acceptance of the request, not the outcome. Poll the settlement report read endpoint:  - **Generated** — `partnerInvoiceId` is present and identifies the new partner invoice. - **Not generated** — generation failed after acceptance. No partner invoice record exists and `partnerInvoiceId` remains absent. Causes include a missing or invalid tax identification number on the partner, a report currency the operator's B2B invoice processor does not support, a tax rate not configured on that processor, and a report whose invoiceable total nets to zero. The failure is reported to the operator through the platform; poll with a bounded number of attempts rather than indefinitely.  Where the operator's B2B invoice processor certifies documents with a fiscal authority, `partnerInvoiceId` appearing means the invoice **record** exists — not that a legally issued document exists. Certification runs as a second asynchronous stage; read `fiscalization.status` on the single-invoice endpoint to follow it to `certified` or `failed`.
- [Partner Settlement Report / Update External ID](https://developers.ampeco.com/reference/partnersettlementreportupdateexternalid.md): Update or clear the external invoice reference ID for a partner settlement report. Used for integration with external accounting systems.
- [Reimbursement record / Issue credit](https://developers.ampeco.com/reference/reimbursementrecordissuecredit.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Creates and returns a new reimbursement record with negated amounts that reverses the original record. A record that is already reversed, or is itself a reversing record, cannot be reversed again.  This is not an accounting credit note against an invoice — reimbursement records are stateless computed entries, so a credit is the reimbursement-domain analogue of a correcting entry.
- [Reimbursement report / Regenerate](https://developers.ampeco.com/reference/reimbursementreportregenerate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Discards the report and rebuilds it from the current reimbursement records on the next generation run. The discarded report id no longer resolves after regeneration; fetch the replacement from the reports listing (its constituent records point to it via `filter[reportId]`). Processing is asynchronous — the response returns immediately with `202 Accepted`.
- [Reservation / Cancel](https://developers.ampeco.com/reference/reservationcancel.md): Cancel a reservation
- [Roaming EMSP / Assign Partner](https://developers.ampeco.com/reference/roamingemspassignpartner.md): Assign or clear the partner mapped to this Roaming EMSP for a platform operator. Send an integer `partnerId` to assign; send `null` to clear. Use `GET /resources/roaming-emsps/v1.0/{roamingEmsp}/partners` to read the current state.
- [Custom Tariff Filters / Set Pricing Data](https://developers.ampeco.com/reference/updatecustomtarifffiltertariff.md): Set the pricing data for a custom tariff filter. This action will update the underlying roaming tariff and create a pricing based on it. The pricing can then be utilized by attaching a markup tariff to the tariff map of the custom tariff filter. The pricing data must follow the OCPI 2.2.1 Tariff object specification.
- [Session / Assign to user](https://developers.ampeco.com/reference/sessionassigntouser.md): Assign a user to a session. This action is only applicable to sessions with Completed billing status that have no user associated with them. This operation can be done only once and is not reversible.
- [Session / Change tariff](https://developers.ampeco.com/reference/sessionchangetariff.md): Change the tariff for a session and trigger recalculation of charging periods. This action supports loyalty program integrations where discounts need to be applied mid-session.  The tariff change is only available when: - Billing status is NOT "Completed" - For running sessions: duration is under 3 hours - For roaming sessions (Ampeco as eMSP): session must be finished and have a CDR received - No recalculation is already in progress - For local charge point sessions: a StartTransaction message must exist
- [Session / Retry Payment](https://developers.ampeco.com/reference/sessionretrypayment.md): Retry failed payment for a session
- [Subscription plan / Replace](https://developers.ampeco.com/reference/subscriptionplanreplace.md): Replace a subscription plan with another one.
- [Tariff / Set Display Information](https://developers.ampeco.com/reference/tariffsetdisplayinformation.md): Create or update tariff display information. This action supports both first-time creation and subsequent updates.  **Field replacement behavior:** Every call fully replaces all four display text fields. Fields not included in the request body, or sent as `null`, are reset to empty. To retain an existing value, you must re-supply it in the request.  **Deprecated fields:** The `defaultPriceInformation` and `defaultPriceInformationOffline` fields are deprecated. Use the tariff group resource to manage these fields instead. The scalar `priceInformation` and `totalCostInformation` fields are deprecated in favor of their `Localized` siblings, which support multi-locale round-tripping.
- [Taxes / Validate VAT number](https://developers.ampeco.com/reference/validatetaxnumber.md): Validate an EU VAT ID against the official VIES (VAT Information Exchange System) API from the European Commission. Returns validation status along with company name and address when available.  The service strips the country code prefix from the VAT number before validation if present (e.g., 'PL5252678750' becomes '5252678750' when validating for country 'PL').
- [Transaction / Create Pre-Authorization](https://developers.ampeco.com/reference/transactioncreatepreauthorization.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta.  Creates a pre-authorisation — a hold, never an immediate charge — for a pending ad hoc transaction, using the payment processor set on the transaction (Worldline or Stripe), and returns what you need to collect the customer's payment. Amount and currency come from the transaction. Repeated calls return the existing pre-authorisation instead of creating a second one.
- [Transaction / Issue Invoice](https://developers.ampeco.com/reference/transactionissueinvoice.md): Issue ad-hoc invoice for the transaction (only if the platform's native invoice integration is used). For Számlázz.hu integration in Hungary, if a fiscalized receipt exists for the transaction, it will be automatically canceled and both the invoice and storno receipt will be sent to the user.
- [Transaction / Resend Invoice](https://developers.ampeco.com/reference/transactionresendinvoice.md): Resend already issued invoice. If the transaction has an associated fiscalized receipt that was automatically canceled (Hungary compliance), both the invoice and the storno receipt will be sent together.
- [Transaction / Update Payment Reference](https://developers.ampeco.com/reference/transactionupdatepaymentreference.md): Link the transaction to external resource where the payment took place.
- [User / Revoke marketing consent](https://developers.ampeco.com/reference/userrevokemarketingconsent.md): Revoke a single user's marketing consent. Records an admin-initiated entry in the consent audit log and an entry in the backend Actions log, attributed to the API token's admin. Use when acting on a GDPR opt-out request received outside the app.  Idempotent: calling on a user who is already opted out returns 202, refreshes the 'receive news and promotions' updated-at timestamp, and records a new entry in the Actions log. The consent audit log only gains entries for consents whose state actually changes.  Partner-scoped tokens: when a partner-scoped token targets a user outside the partner's visibility, the response is 403 (consistent with other user-action endpoints) — the user-edit ability is denied because the token's admin cannot act on the target user.
- [User / Activate subscription](https://developers.ampeco.com/reference/useractivatesubscription.md): Activate a subscription to a user
- [User / Add Balance](https://developers.ampeco.com/reference/useraddbalance.md): Add to the current balance of the user
- [User / Apply Custom Fee](https://developers.ampeco.com/reference/userapplycustomfee.md): Apply custom fee for a user
- [User / Cancel subscription](https://developers.ampeco.com/reference/usercancelsubscription.md): Cancel a subscription to a user
- [User / Change Status](https://developers.ampeco.com/reference/userchangestatus.md): Set the status for a user
- [User / Clear subscription amount due](https://developers.ampeco.com/reference/userclearsubscriptionamountdue.md): Clear a user's subscription amount due. Any unsettled transactions related to the user's current subscription — such as fees and charging sessions — will be set to an amount of 0. This operation is irreversible and cannot run while a subscription payment is in progress.
- [User / Get total eligible coupon energy](https://developers.ampeco.com/reference/usergettotaleligiblecouponenergy.md): Returns the total remaining energy (in watt-hours) and coupon count from the user's energy coupons that are eligible for use at a specific EVSE. A coupon is considered eligible when it is active, has remaining energy, is within its validity period, and satisfies all restrictions configured on the coupon — including EVSE type (AC/DC), country allowance, partner allowance, and home charge point restrictions. Use this endpoint to check how much coupon-based energy a user can consume before starting a charging session at a given EVSE.
- [User / Subscribe to plan](https://developers.ampeco.com/reference/usersubscribetoplan.md): Subscribe a user to a plan and collect payment.  The subscription and installment are created immediately. Payment collection happens asynchronously and does not affect the response. If `paymentMethodId` is provided, that payment method is used exclusively. If omitted, the system uses automatic payment method resolution. For free pre-paid plans (price = 0) and post-paid plans, payment is skipped.  If the user already has an active subscription to a different plan, that subscription is cancelled and the new one is activated.
- [Subscription billing period / Retry payment](https://developers.ampeco.com/reference/subscriptionbillingperiodretrypayment.md): Retry failed payment for a subscription billing period
- [User / Export All Private Data](https://developers.ampeco.com/reference/userexportallprivatedata.md): Export all private data
- [User / Redeem Voucher](https://developers.ampeco.com/reference/userredeemvoucher.md): Apply a voucher to a user
- [Communication logs / Listing](https://developers.ampeco.com/reference/communicationlogslisting.md): Get all communication logs with optional filtering and pagination.  Returns raw communication payloads including request/response data. For optimal performance, always specify `filter[createdAfter]` and `filter[createdBefore]` to limit the time range.
- [Communication log / Read](https://developers.ampeco.com/reference/communicationlogread.md): Get a single communication log entry by ID.
- [OCPI Logs / Listing](https://developers.ampeco.com/reference/listocpilogs.md): Get paginated list of OCPI communication logs with optional filtering and pagination.  Returns raw OCPI communication payloads including request/response data. For optimal performance, always specify `filter[createdAfter]` and `filter[createdBefore]` to limit the time range. The maximum allowed date range is 30 days. If no date range is specified, the last 30 days will be returned.
- [OCPI Log / Read](https://developers.ampeco.com/reference/readocpilog.md): Get a single OCPI log entry by ID.
- [Notifications / Subscribe](https://developers.ampeco.com/reference/notificationssubscribedeprecated.md): Subscribe for a webhook. Each notification sent to the webhook will be retried a number of times and will be rate limited. The rate limits, retries and retry intervals will be configured by the platform administrator.  Each notification callback will contain a signature in the `X-Signature` request header which can be verified using SHA256-HMAC on the body of the request using the access token that was used when creating the notification as key.
- [Notifications / Listing](https://developers.ampeco.com/reference/notificationslistingdeprecated.md)
- [Notifications / Read](https://developers.ampeco.com/reference/notificationsreaddeprecated.md): Get a notification
- [Notifications / Update](https://developers.ampeco.com/reference/notificationsupdatedeprecated.md): Update a notification
- [Notifications / Unsubscribe](https://developers.ampeco.com/reference/notificationsunsubscribedeprecated.md): Unsubscribe for a webhook
- [Notifications / Subscribe](https://developers.ampeco.com/reference/notificationssubscribe.md): Subscribe for a webhook or kafka events. Each notification sent to the webhook/kafka will be retried a number of times and will be rate limited. The rate limits, retries and retry intervals will be configured by the platform administrator.  Each notification callback will contain a signature in the `X-Signature` request header which can be verified using SHA256-HMAC on the body of the request using the access token that was used when creating the notification as key.
- [Notifications / Listing](https://developers.ampeco.com/reference/notificationslisting.md)
- [Notification / Read](https://developers.ampeco.com/reference/notificationread.md): Get a notification
- [Notifications / Update](https://developers.ampeco.com/reference/notificationscreate.md): Update a notification
- [Notifications / Unsubscribe](https://developers.ampeco.com/reference/notificationsunsubscribe.md): Unsubscribe for a notification
- [OAuth token revocation](https://developers.ampeco.com/reference/oauthtokenrevoke.md): Revoke a short-lived bearer access token per RFC 7009 without rotating the underlying client credential.  **Client authentication.** Two methods are supported: - **HTTP Basic** (recommended): send `client_id:client_secret` Base64-encoded in the `Authorization: Basic ...` header. - **POST body**: include `client_id` and `client_secret` in the request body alongside `token`.  Sending credentials via both methods in the same request is rejected with `invalid_request`. `Authorization: Bearer` is not accepted for this endpoint.  **Request format.** Both `application/x-www-form-urlencoded` and `application/json` are accepted.
- [OAuth / Token Exchange](https://developers.ampeco.com/reference/oauthtokenexchange.md): Exchange long-lived client credentials for a short-lived bearer access token per RFC 6749 Section 4.4 (Client Credentials Grant).  **Client authentication.** Two methods are supported (RFC 6749 Section 2.3): - **HTTP Basic** (recommended): send `client_id:client_secret` Base64-encoded in the `Authorization: Basic ...` header. The request body must contain only `grant_type=client_credentials`. - **POST body**: include `client_id` and `client_secret` in the request body alongside `grant_type=client_credentials`.  Sending credentials via both methods in the same request is rejected with `invalid_request`.  **Request format.** Both `application/x-www-form-urlencoded` and `application/json` are accepted.
- [Admins / Listing](https://developers.ampeco.com/reference/adminlist.md): Get a list of administrators.  Returns administrators belonging to the same operator as the API token. Results are paginated using cursor-based pagination.
- [Admin / Read](https://developers.ampeco.com/reference/adminread.md): Get administrator details by ID.  Returns administrator information including organizational context (if applicable), role, and optionally permissions.  **Admin types:** The admin type can be determined by which optional ID field is present: - `partnerId` - Admin belongs to a partner organization - `subOperatorId` - Admin belongs to a sub-operator organization - `installationAndMaintenanceCompanyId` - Admin belongs to an I&M company - None of the above - Operator-level administrator  **SSO field:** The `externalSsoId` field is present when the administrator has SSO authentication enabled.  **Permissions include:** Use `?include[]=permissions` to include the administrator's permissions in the response.
- [Admin / Permissions](https://developers.ampeco.com/reference/adminpermissions.md): Get administrator permissions.  Returns a list of permission names assigned to the administrator. This is an alternative to using `?include[]=permissions` on the admin read endpoint.
- [Authorization / Read](https://developers.ampeco.com/reference/authorizationreaddeprecated.md)
- [Authorizations / Listing](https://developers.ampeco.com/reference/authorizationslisting.md): **Deprecated:** Use v2.1 endpoint instead. This endpoint does not distinguish between RFID and MAC address (Autocharge) authorizations - both return `id_tag` as the method.
- [Authorization / Read](https://developers.ampeco.com/reference/authorizationread.md): **Deprecated:** Use v2.1 endpoint instead. This endpoint does not distinguish between RFID and MAC address (Autocharge) authorizations - both return `id_tag` as the method.
- [Authorizations / Listing](https://developers.ampeco.com/reference/authorizationslistingv2_1.md): Get all authorizations
- [Authorization / Read](https://developers.ampeco.com/reference/authorizationreadv2_1.md)
- [Booking Requests / Listing](https://developers.ampeco.com/reference/bookingrequestslisting.md): Get all booking requests
- [Booking Request / Create](https://developers.ampeco.com/reference/bookingrequestcreate.md): Create a new booking request. If you want to find the available slots for a given location use the Actions / Location / Check Booking Availability
- [Booking Request / Read](https://developers.ampeco.com/reference/bookingrequestread.md): Get information for a booking request by ID
- [Bookings / Listing](https://developers.ampeco.com/reference/bookingslisting.md): Get all bookings
- [Booking / Read](https://developers.ampeco.com/reference/bookingread.md): Get information for a booking by ID
- [CDRs / Listing](https://developers.ampeco.com/reference/cdrslisting.md): Get all CDRs
- [CDR / Read](https://developers.ampeco.com/reference/cdrread.md): Get a CDR
- [Charge Point Downtime Periods / Listing](https://developers.ampeco.com/reference/chargepointdowntimeperiodslisting.md): Get all Charge Point Downtime Periods
- [Charge Point Downtime Period / Create](https://developers.ampeco.com/reference/chargepointdowntimeperiodcreate.md): Create Manual Exempt Charge Point Downtime Period
- [Charge Point Downtime Period / Read](https://developers.ampeco.com/reference/chargepointdowntimeperiodread.md): Get Charge Point Downtime Period
- [Charge Point Downtime Period / Update](https://developers.ampeco.com/reference/chargepointdowntimeperiodupdate.md): Update Charge Point Downtime Period
- [Charge Point Downtime Period / Delete](https://developers.ampeco.com/reference/chargepointdowntimeperioddelete.md): Delete Manual Created Charge Point Downtime Period
- [Charge Point Downtime Period / Status Log](https://developers.ampeco.com/reference/chargepointdowntimeperiodstatuslog.md): Get the StatusLog entry that triggered this downtime period
- [Charge Point Models / Listing](https://developers.ampeco.com/reference/chargepointmodelslisting.md): Get all Charge Point Models
- [Charge Point Model / Create](https://developers.ampeco.com/reference/chargepointmodelcreate.md): Create new Charge Point Model
- [Charge Point Model / Read](https://developers.ampeco.com/reference/chargepointmodelread.md): Get a Charge Point Model
- [Charge Point Model / Update](https://developers.ampeco.com/reference/chargepointmodelupdate.md): Charge Point Model
- [Charge Point Model / Delete](https://developers.ampeco.com/reference/chargepointmodeldelete.md): Delete a Charge Point Model
- [Charge Point Models / Listing](https://developers.ampeco.com/reference/chargepointmodelslistingdeprecated.md): Get all Charge Point Models
- [Charge Point Model / Create](https://developers.ampeco.com/reference/chargepointmodelcreatedeprecated.md): Create new Charge Point Model
- [Charge Point Model / Read](https://developers.ampeco.com/reference/chargepointmodelreaddeprecated.md): Get a Charge Point Model
- [Charge Point Model / Update](https://developers.ampeco.com/reference/chargepointmodelupdatedeprecated.md): Charge Point Model
- [Charge Point Model / Delete](https://developers.ampeco.com/reference/chargepointmodeldeletedeprecated.md): Delete a Charge Point Model
- [Charge Point Vendors / Listing](https://developers.ampeco.com/reference/chargepointvendorslisting.md): Get all Charge Point Vendors
- [Charge Point Vendor / Create](https://developers.ampeco.com/reference/chargepointvendorcreate.md): Create new Charge Point Vendor
- [Charge Point Vendor / Read](https://developers.ampeco.com/reference/chargepointvendorread.md): Get a Charge Point Vendor
- [Charge Point Vendor / Update](https://developers.ampeco.com/reference/chargepointvendorupdate.md): Charge Point Vendor
- [Charge Point Vendor / Delete](https://developers.ampeco.com/reference/chargepointvendordelete.md): Delete a Charge Point Vendor
- [Charge Point Vendors / Listing](https://developers.ampeco.com/reference/chargepointvendorslistingdeprecated.md): Get all Charge Point Vendors
- [Charge Point Vendor / Create](https://developers.ampeco.com/reference/chargepointvendorcreatedeprecated.md): Create new Charge Point Vendor
- [Charge Point Vendor / Read](https://developers.ampeco.com/reference/chargepointvendorreaddeprecated.md): Get a Charge Point Vendor
- [Charge Point Vendor / Update](https://developers.ampeco.com/reference/chargepointvendorupdatedeprecated.md): Charge Point Vendor
- [Charge Point Vendor / Delete](https://developers.ampeco.com/reference/chargepointvendordeletedeprecated.md): Delete a Charge Point Vendor
- [Charge Points / Listing](https://developers.ampeco.com/reference/chargepointslistingdeprecated.md): Get all charge points
- [Charge Point / Create](https://developers.ampeco.com/reference/chargepointcreatedeprecated.md): Create new charge point
- [Charge Point / Read](https://developers.ampeco.com/reference/chargepointreaddeprecated.md): Get a charge point
- [Charge Point / Update](https://developers.ampeco.com/reference/chargepointupdatedeprecated.md): Update a charge point
- [Charge Point / Delete](https://developers.ampeco.com/reference/chargepointdeletedeprecated.md): Delete a charge point
- [Charge Point / Configurations / Listing](https://developers.ampeco.com/reference/chargepointconfigurationslistingdeprecated.md): Get a charge point's all cached configurations
- [Charge Point / Configuration / Read](https://developers.ampeco.com/reference/chargepointconfigurationreaddeprecated.md): Get a charge point's cached configuration for a single key
- [Charge Point / Configuration / Update](https://developers.ampeco.com/reference/chargepointconfigurationupdatedeprecated.md): Update a charge point's configuration. The configuration is applied directly to the charge point and you will get response code 406 in case the application fails
- [Charge Point / Status / Read](https://developers.ampeco.com/reference/chargepointstatusread.md): Get a charge point's status
- [Charge Point / Create](https://developers.ampeco.com/reference/chargepointcreate.md): Create new charge point
- [Charge Points / Listing](https://developers.ampeco.com/reference/chargepointslisting.md): Get all charge points
- [Charge Point / Update](https://developers.ampeco.com/reference/chargepointupdate.md): Update a charge point
- [Charge Point / Read](https://developers.ampeco.com/reference/chargepointread.md): Get a charge point
- [Charge Point / Delete](https://developers.ampeco.com/reference/chargepointdelete.md): Delete a charge point
- [Charge Point / Available personal smart charging modes / Listing](https://developers.ampeco.com/reference/chargepointavailablepersonalsmartchargingmodeslisting.md): Get all available personal smart charging modes
- [Charge Point / Configurations / Listing](https://developers.ampeco.com/reference/chargepointconfigurationslisting.md): Get a charge point's all cached configurations
- [Charge Point / Configuration / Read](https://developers.ampeco.com/reference/chargepointconfigurationread.md): Get a charge point's cached configuration for a single key
- [Charge Point / Configuration / Update](https://developers.ampeco.com/reference/chargepointconfigurationupdate.md): Update a charge point's configuration. The configuration is applied directly to the charge point and you will get response code 406 in case the application fails
- [Charge Point / EVSE / Create](https://developers.ampeco.com/reference/chargepointevsecreate.md): Create new EVSE within the Charge Point
- [Charge Point / EVSEs / Listing](https://developers.ampeco.com/reference/chargepointevseslisting.md): Get all EVSEs of the Charge Point
- [Charge Point / EVSE / Update](https://developers.ampeco.com/reference/chargepointevseupdate.md): Update an EVSE within the Charge Point
- [Charge Point / EVSE / Read](https://developers.ampeco.com/reference/chargepointevseread.md): Get an EVSE from a Charge Point
- [Charge Point / EVSE / Delete](https://developers.ampeco.com/reference/chargepointevsedelete.md): Delete an EVSE
- [Charge Point / Evse / Connectors / Listing](https://developers.ampeco.com/reference/chargepointevseconnectorslisting.md): Get a charge point evse's all connectors
- [Charge Points / Evse / Connector / Create](https://developers.ampeco.com/reference/chargepointevseconnectorcreate.md): Create a charge point evse's connector
- [Charge Points / Evse / Connector / Read](https://developers.ampeco.com/reference/chargepointevseconnectorread.md): Get a charge point evse's connector
- [Charge Points / Evse / Connector / Update](https://developers.ampeco.com/reference/chargepointevseconnectorupdate.md): Update a charge point evse's connector
- [Charge Points / Evse / Connector / Delete](https://developers.ampeco.com/reference/chargepointevseconnectordelete.md): Delete a charge point evse's connector
- [Charge Point / Hardware Status Logs / Listing](https://developers.ampeco.com/reference/listchargepointhardwarestatuslogs.md): Get paginated list of hardware status logs for a charge point with optional status and date filtering
- [Charge Point / Latest Hardware Status Log](https://developers.ampeco.com/reference/getchargepointlatesthardwarestatuslog.md): Get the latest hardware status log entry for a charge point
- [Charge Point / Latest Network Status Log](https://developers.ampeco.com/reference/getchargepointlatestnetworkstatuslog.md): Get the latest network status log entry for a charge point
- [Charge Point / Network Status Logs / Listing](https://developers.ampeco.com/reference/listchargepointnetworkstatuslogs.md): Get paginated list of network status logs for a charge point with optional date filtering
- [Charge Point / Notes / Listing](https://developers.ampeco.com/reference/chargepointnoteslisting.md): List all notes for a specific charge point.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [Charge Point / Note / Create](https://developers.ampeco.com/reference/chargepointnotecreate.md): Create a new note for a specific charge point.  **Required permission:** `Notes.create`
- [Charge Point / Note / Read](https://developers.ampeco.com/reference/chargepointnoteshow.md): Get a specific note for a charge point.  **Required permission:** `Notes.view`
- [Charge Point / Note / Update](https://developers.ampeco.com/reference/chargepointnoteupdate.md): Update a specific note for a charge point.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [Charge Point / Note / Delete](https://developers.ampeco.com/reference/chargepointnotedelete.md): Delete a specific note from a charge point.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [Charge Point / Personal smart charging preferences / Read](https://developers.ampeco.com/reference/chargepointpersonalsmartchargingpreferencesread.md): Get personal smart charging preferences of the charge point
- [Charge Point / Personal smart charging preferences / Update](https://developers.ampeco.com/reference/personalsmartchargingpreferencesupdate.md): Update personal smart charging preferences
- [Charge Point / Shared Partners / Listing](https://developers.ampeco.com/reference/chargepointsharedpartnerslisting.md): Get all Shared Partners of the Charge Point
- [Charge Point / Shared Partners / Update](https://developers.ampeco.com/reference/chargepointsharedpartnerssync.md): Set the Shared Partners of the Charge Point. Attach Shared Partners within the Charge Point. The charge point must have an owner associated and its `access_type` must be `private`. Grants access to this Partner to the charge point. This allows their invited users with access to private CPs to also access this CP. It also gives view-only access to the selected Partner's admins to this CP.
- [Charge point / share / create](https://developers.ampeco.com/reference/chargepointsharecreate.md): Create a new share within the charge point
- [Charge point / shares / listing](https://developers.ampeco.com/reference/chargepointshareslisting.md): Get all shares of the charge point
- [Charge point / share / read](https://developers.ampeco.com/reference/chargepointshareread.md): Get a share from a charge point
- [Charge point / share / update](https://developers.ampeco.com/reference/chargepointshareupdate.md): Update a share
- [Charge point / share / delete](https://developers.ampeco.com/reference/charegpointsharedelete.md): Delete a share
- [Charge Point / Smart Charging / Update](https://developers.ampeco.com/reference/chargepointsmartchargingupdate.md): Update smart charging details for the charge point
- [Circuits / Listing](https://developers.ampeco.com/reference/circuitslistingdeprecated.md): Get all circuits
- [Circuit / Create](https://developers.ampeco.com/reference/circuitcreatedeprecated.md): Create new circuits
- [Circuit / Read](https://developers.ampeco.com/reference/circuitreaddeprecated.md): Get a circuit
- [Circuit / Update](https://developers.ampeco.com/reference/circuitupdatedeprecated.md): Update a circuit
- [Circuit / Delete](https://developers.ampeco.com/reference/circuitdeletedeprecated.md): Delete a circuit.  If the circuit is part of a disabled flexibility asset, both the circuit and the associated flexibility asset will be deleted.  If the circuit is part of an enabled flexibility asset, the deletion will be rejected with a 409 Conflict status code.
- [Circuit / Consumption (all phases)](https://developers.ampeco.com/reference/circuitconsumptionallphasesdeprecated.md): Get the consumption of a circuit for each phase
- [Circuit / Consumption (phase)](https://developers.ampeco.com/reference/circuitconsumptionphasedeprecated.md): Get the consumption of a circuit for a single phase
- [Circuits / Listing](https://developers.ampeco.com/reference/circuitslisting.md): Get all circuits
- [Circuit / Create](https://developers.ampeco.com/reference/circuitcreate.md): Create a new circuit
- [Circuit / Read](https://developers.ampeco.com/reference/circuitread.md): Get a circuit
- [Circuit / Update](https://developers.ampeco.com/reference/circuitupdate.md): Update a circuit
- [Circuit / Delete](https://developers.ampeco.com/reference/circuitdelete.md): Delete a circuit.  If the circuit is part of a disabled flexibility asset, both the circuit and the associated flexibility asset will be deleted.  If the circuit is part of an enabled flexibility asset, the deletion will be rejected with a 409 Conflict status code.
- [Circuit / Charge Point Priorities / Listing](https://developers.ampeco.com/reference/circuitchargepointprioritieslisting.md): Get all circuit's charge point priorities
- [Circuit / Consumption](https://developers.ampeco.com/reference/circuitconsumption.md): Get the consumption of a circuit for each phase
- [Circuit / Schedule / Read](https://developers.ampeco.com/reference/circuitscheduleread.md): Get a circuit's schedule configuration
- [Circuit / Schedule / Create or Update](https://developers.ampeco.com/reference/circuitschedulecreateorupdate.md): Create or replace a circuit's schedule configuration
- [Circuit / Schedule / Delete](https://developers.ampeco.com/reference/circuitscheduledelete.md): Clear a circuit's schedule configuration
- [Circuit / SoC Priorities / Listing](https://developers.ampeco.com/reference/circuitsocprioritieslisting.md): Get a circuit's SoC priority
- [Circuit / Unmanaged Load / Read](https://developers.ampeco.com/reference/circuitunmanagedloadread.md): Get a circuit's unmanaged load
- [Circuits / User Priorities / Listing](https://developers.ampeco.com/reference/circuituserprioritieslisting.md): Get all circuit's user priorities
- [Circuits / User Priority / Create](https://developers.ampeco.com/reference/circuituserprioritycreate.md): Create a circuit's user priority
- [Circuits / User Priority / Read](https://developers.ampeco.com/reference/circuituserpriorityread.md): Get a circuit's user priority
- [Circuits / User Priority / Update](https://developers.ampeco.com/reference/circuituserpriorityupdate.md): Update a circuit's user priority
- [Circuits / User Priority / Delete](https://developers.ampeco.com/reference/circuituserprioritydelete.md): Delete a circuit's user priority
- [Configuration Template / Listing](https://developers.ampeco.com/reference/listconfigurationtemplates.md): Get all Configuration Templates
- [Configuration Template / Create](https://developers.ampeco.com/reference/createconfigurationtemplate.md): Create new Configuration Template
- [Configuration Template / Update](https://developers.ampeco.com/reference/updateconfigurationtemplate.md): Update Configuration Template
- [Configuration Template / Read](https://developers.ampeco.com/reference/getconfigurationtemplate.md): Get Configuration Template
- [Configuration Template / Delete](https://developers.ampeco.com/reference/deleteconfigurationtemplate.md): Delete Configuration Template
- [Configuration Template Variable / Listing](https://developers.ampeco.com/reference/configurationtemplatevariablelisting.md): Get all Configuration Template Variables
- [Configuration Template Variable / Create](https://developers.ampeco.com/reference/configurationtemplatevariablecreate.md): Create a new Configuration Template Variable
- [Configuration Template Variable / Update](https://developers.ampeco.com/reference/configurationtemplatevariableupdate.md): Update a Configuration Template Variable
- [Configuration Template Variable / Delete](https://developers.ampeco.com/reference/configurationtemplatevariabledelete.md): Delete a Configuration Template Variable
- [Consent History / Listing](https://developers.ampeco.com/reference/consenthistorylisting.md): Retrieve the full consent history log showing all consent actions (agreements and rejections) performed by users over time. Results are ordered by actionAt descending (most recent first).
- [Consents / Listing](https://developers.ampeco.com/reference/consentslisting.md): Retrieve consent data for users
- [Consents / Create](https://developers.ampeco.com/reference/consentscreate.md): Create user consent for a specific term version. If a consent already exists for the given user and term version combination, the request will fail with a 409 Conflict error.
- [Contact details / Read](https://developers.ampeco.com/reference/contactdetailsread.md): Get the contact details
- [Contact details / Update](https://developers.ampeco.com/reference/contactdetailsupdate.md): Update the contact details
- [Contact details / Delete](https://developers.ampeco.com/reference/contactdetailsdelete.md): Delete contact details
- [Currencies / Listing](https://developers.ampeco.com/reference/currencieslisting.md)
- [Currency / Create](https://developers.ampeco.com/reference/currencycreate.md): Create currency
- [Currency / Read](https://developers.ampeco.com/reference/currencyread.md)
- [Currency / Update](https://developers.ampeco.com/reference/currencyupdate.md): Update a currency
- [Currency / Delete](https://developers.ampeco.com/reference/currencydeletedeprecated.md): Delete a currency
- [Currency Rate / Create](https://developers.ampeco.com/reference/createcurrencyrate.md): Create new Currency Rate
- [Currency Rate / Listing](https://developers.ampeco.com/reference/listcurrencyrates.md): Get all Currency Rates
- [Currency Rate / Update](https://developers.ampeco.com/reference/updatecurrencyrate.md): Update Currency Rate
- [Currency Rate / Read](https://developers.ampeco.com/reference/getcurrencyrate.md): Get Currency Rate
- [Currency Rate / Delete](https://developers.ampeco.com/reference/deletecurrencyrate.md): Delete Currency Rate
- [Custom Fees / Listing](https://developers.ampeco.com/reference/customfeeslisting.md): Get all custom fees
- [Custom Fee / Read](https://developers.ampeco.com/reference/customfeeread.md): Get a single custom fee
- [Downtime Period Notices / Listing](https://developers.ampeco.com/reference/getdowntimeperiodnotices.md): Get all Downtime Period Notices
- [Downtime Period Notices / Create](https://developers.ampeco.com/reference/postdowntimeperiodnotice.md): Create Downtime Period Notice
- [Downtime Period Notices / Read](https://developers.ampeco.com/reference/getdowntimeperiodnotice.md): Get Downtime Period Notice
- [Downtime Period Notices / Update](https://developers.ampeco.com/reference/patchdowntimeperiodnotice.md): Update Downtime Period Notice
- [Downtime Period Notices / Delete](https://developers.ampeco.com/reference/deletedowntimeperiodnotice.md): Delete Downtime Period Notice
- [Electricity Meters / Listing](https://developers.ampeco.com/reference/electricitymeterslising.md): Get all electricity meters
- [Electricity Meter / Create](https://developers.ampeco.com/reference/electricitymetercreate.md): Create a new electricity meter
- [Electricity Meter / Read](https://developers.ampeco.com/reference/electricitymeterread.md): Get information for an electricity meter by ID
- [Electricity Meter / Update](https://developers.ampeco.com/reference/electricitymeterupdate.md): Update electricity meter
- [Electricity Meter / Delete](https://developers.ampeco.com/reference/electricitymeterdelete.md): Delete an electricity meter.
- [Electricity rates / Listing](https://developers.ampeco.com/reference/electricityrateslistingdeprecated.md): Get all Electricity rates
- [Electricity rate / Create](https://developers.ampeco.com/reference/electricityratecreatedeprecated.md): Create a new Electricity rate
- [Electricity rate / Read](https://developers.ampeco.com/reference/electricityratereaddeprecated.md): Get a single Electricity rate
- [Electricity rate / Update](https://developers.ampeco.com/reference/electricityrateupdatedeprecated.md): Update a Electricity rate
- [Electricity rate / Delete](https://developers.ampeco.com/reference/electricityratedeletedeprecated.md): Delete a Electricity rate
- [Electricity rates / Listing](https://developers.ampeco.com/reference/electricityrateslisting.md): Get all Electricity rates
- [Electricity rate / Create](https://developers.ampeco.com/reference/electricityratecreate.md): Create a new Electricity rate
- [Electricity rate / Read](https://developers.ampeco.com/reference/electricityrateread.md): Get a single Electricity rate
- [Electricity rate / Update](https://developers.ampeco.com/reference/electricityrateupdate.md): Update a Electricity rate
- [Electricity rate / Delete](https://developers.ampeco.com/reference/electricityratedelete.md): Delete a Electricity rate
- [Electricity rate / Energy Mix / Read](https://developers.ampeco.com/reference/electricityrateenergymixread.md): Get an electricity rate energy mix
- [Electricity rate / Energy Mix / Update](https://developers.ampeco.com/reference/electricityrateenergymixupdate.md): Set an electricity rate energy mix. By default the energy mix generated with creation of the electricity rate is filled with 0.
- [Electricity rate / Price periods / Listing](https://developers.ampeco.com/reference/electricityratepriceperiodslisting.md): List all of the configured price period days (including week days and dates)
- [Electricity rate / Price periods / Date / Listing](https://developers.ampeco.com/reference/electricityratepriceperiodsdatelisting.md): List all of the configured price period dates
- [Electricity rate / Price periods / Date / Read](https://developers.ampeco.com/reference/electricityratepriceperiodsdateread.md): Get the price periods for a specific date.
- [Electricity rate / Price periods / Date / Create or update](https://developers.ampeco.com/reference/electricityratepriceperiodsdatecreateorupdate.md): Update the price periods for a specific date. This operation will overwrite all existing periods for the given date, so a complete list must be provided
- [Electricity rate / Price periods / Date / Delete](https://developers.ampeco.com/reference/electricityratepriceperiodsdatedelete.md): Delete the price periods for a specific date.
- [Electricity rate / Price periods / Week day / Listing](https://developers.ampeco.com/reference/electricityratepriceperiodsweekdaylisting.md): List all of the configured price period week days
- [Electricity rate / Price periods / Week day / Read](https://developers.ampeco.com/reference/electricityratepriceperiodsweekdayread.md): Get the price periods for a specific week day.
- [Electricity rate / Price periods / Week day / Create or update](https://developers.ampeco.com/reference/electricityratepriceperiodsweekdaycreateaorupdate.md): Update the price periods for a specific week day. This operation will overwrite all existing periods for the given day, so a complete list must be provided
- [Electricity rate / Price periods / Week day / Delete](https://developers.ampeco.com/reference/electricityratepriceperiodsweekdaydelete.md): Delete the price periods for a specific week day.
- [Energy coupon templates / Listing](https://developers.ampeco.com/reference/energycoupontemplateslisting.md): Get all energy coupon templates with optional filtering
- [Energy coupon templates / Create](https://developers.ampeco.com/reference/energycoupontemplatecreate.md): Create a new energy coupon template for promotional campaigns
- [Energy coupon template / Read](https://developers.ampeco.com/reference/energycoupontemplateread.md): Get a single energy coupon template by ID, including redemption statistics
- [Energy coupon template / Update](https://developers.ampeco.com/reference/energycoupontemplateupdate.md): Update an energy coupon template. Only non-structural fields can be updated.
- [Energy coupons / Listing](https://developers.ampeco.com/reference/energycouponslisting.md): Get all energy coupons
- [Energy coupon / Create](https://developers.ampeco.com/reference/energycouponcreate.md): Create a single-use energy coupon, optionally assigned to a specific user. When userId is omitted, the coupon is created with "unredeemed" status.
- [Energy coupon / Read](https://developers.ampeco.com/reference/energycouponread.md): Get a single energy coupon with optional session data
- [Energy coupon / Session consumption records](https://developers.ampeco.com/reference/energycouponsessionconsumptionrecords.md): Returns a breakdown of how a coupon's energy was consumed across charging sessions. Each record represents the amount of energy drawn from this coupon by a specific session.
- [EVSE Downtime Periods / Listing](https://developers.ampeco.com/reference/evsedowntimeperiodslisting.md): Get all EVSE Downtime Periods
- [EVSE Downtime Period / Create](https://developers.ampeco.com/reference/evsedowntimeperiodcreate.md): Create Manual Exempt EVSE Downtime Period
- [EVSE Downtime Period / Read](https://developers.ampeco.com/reference/evsedowntimeperiodread.md): Get EVSE Downtime Period
- [EVSE Downtime Period / Update](https://developers.ampeco.com/reference/evsedowntimeperiodupdate.md): Update EVSE Downtime Period
- [EVSE Downtime Period / Delete](https://developers.ampeco.com/reference/evsedowntimeperioddelete.md): Delete Manual Created EVSE Downtime Period
- [EVSE Downtime Period / Status Log](https://developers.ampeco.com/reference/evsedowntimeperiodstatuslog.md): Get the StatusLog entry that triggered this downtime period
- [EVSEs / Listing](https://developers.ampeco.com/reference/evseslistingdeprecated.md): Get all EVSEs
- [EVSE / Read](https://developers.ampeco.com/reference/evsereaddeprecated.md): Get a EVSE
- [EVSE / Update](https://developers.ampeco.com/reference/evseupdatedeprecated.md): Update a EVSE
- [EVSE / Hardware Status Logs / Listing](https://developers.ampeco.com/reference/listevsehardwarestatuslogs.md): Get paginated list of hardware status logs for an EVSE with optional status and date filtering
- [EVSE / Latest Hardware Status Log](https://developers.ampeco.com/reference/getevselatesthardwarestatuslog.md): Get the latest hardware status log entry for an EVSE
- [EVSE / Notes / Listing](https://developers.ampeco.com/reference/evsenoteslisting.md): List all notes for a specific EVSE.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [EVSE / Note / Create](https://developers.ampeco.com/reference/evsenotecreate.md): Create a new note for a specific EVSE.  **Required permission:** `Notes.create`
- [EVSE / Note / Read](https://developers.ampeco.com/reference/evsenoteshow.md): Get a specific note for an EVSE.  **Required permission:** `Notes.view`
- [EVSE / Note / Update](https://developers.ampeco.com/reference/evsenoteupdate.md): Update a specific note for an EVSE.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [EVSE / Note / Delete](https://developers.ampeco.com/reference/evsenotedelete.md): Delete a specific note from an EVSE.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [EVSE / Create](https://developers.ampeco.com/reference/evsecreate.md): Create new EVSE
- [EVSEs / Listing](https://developers.ampeco.com/reference/evseslisting.md): Get all EVSEs
- [EVSE / Update](https://developers.ampeco.com/reference/evseupdate.md): Update an EVSE
- [EVSE / Read](https://developers.ampeco.com/reference/evseread.md): Get an EVSE
- [EVSE / Delete](https://developers.ampeco.com/reference/evsedelete.md): Delete an EVSE
- [FAQs / Listing](https://developers.ampeco.com/reference/faqslisting.md): Get all FAQs
- [FAQ / Create](https://developers.ampeco.com/reference/faqcreate.md): Create new FAQ
- [FAQ / Read](https://developers.ampeco.com/reference/faqread.md): Get a FAQ
- [FAQ / Update](https://developers.ampeco.com/reference/faqupdate.md): FAQs
- [FAQ / Delete](https://developers.ampeco.com/reference/faqdelete.md): Delete a FAQ
- [Firmware Versions / Listing](https://developers.ampeco.com/reference/firmwareversionslisting.md): Get all Firmware Versions
- [Firmware Version / Read](https://developers.ampeco.com/reference/firmwareversionread.md): Get a Firmware Version
- [Firmware Version / Attached Models](https://developers.ampeco.com/reference/firmwareversionattachedmodels.md): Get all charge point models attached to this firmware version
- [Flexibility Activation Requests / Listing](https://developers.ampeco.com/reference/listflexibilityactivationrequests.md): Get a list of Flexibility Requests
- [Flexibility Activation Requests / Read](https://developers.ampeco.com/reference/getflexibilityactivationrequest.md): Get a flexibility activation request
- [Flexibility Assets / Create](https://developers.ampeco.com/reference/createflexibilityasset.md): Create new flexibility asset
- [Flexibility Assets / Listing](https://developers.ampeco.com/reference/listflexibilityassets.md): Get a list of Flexibility Assets
- [Flexibility Assets / Update](https://developers.ampeco.com/reference/updateflexibilityasset.md): Update a flexibility asset. Changing the circuit will permanently delete all existing historical and forecast time series data and regenerate new data based on the selected circuit.
- [Flexibility Assets / Read](https://developers.ampeco.com/reference/getflexibilityasset.md): Get a flexibility asset
- [Flexibility Assets / Delete](https://developers.ampeco.com/reference/deleteflexibilityasset.md): Delete a flexibility asset
- [Flexibility Assets / Historical Time Series](https://developers.ampeco.com/reference/gethistoricaltimeseries.md): Get Historical Time Series for a Flexibility Asset
- [Flexibility Assets / Time Series Forecast](https://developers.ampeco.com/reference/gettimeseriesforecast.md): Get Time Series Forecast for a Flexibility Asset
- [Id Tags / Listing](https://developers.ampeco.com/reference/idtagslisting.md): Get all id tags
- [Id Tag / Create](https://developers.ampeco.com/reference/idtagcreate.md): Create new Id Tag
- [Id Tag / Read](https://developers.ampeco.com/reference/idtagread.md): Get a Id Tag
- [Id Tag / Update](https://developers.ampeco.com/reference/idtagupdate.md): Update a Id Tag
- [Id Tag / Delete](https://developers.ampeco.com/reference/idtagdelete.md): Delete a Id Tag
- [ID tag / Notes / Listing](https://developers.ampeco.com/reference/idtagnoteslisting.md): List all notes for a specific ID tag.  Notes are returned with pinned notes first, then ordered by ID descending.  **Required permission:** `Notes.view`
- [ID tag / Note / Create](https://developers.ampeco.com/reference/idtagnotecreate.md): Create a new note for a specific ID tag.  **Required permission:** `Notes.create`
- [ID tag / Note / Read](https://developers.ampeco.com/reference/idtagnoteread.md): Get a specific note for an ID tag.  **Required permission:** `Notes.view`
- [ID tag / Note / Update](https://developers.ampeco.com/reference/idtagnoteupdate.md): Update a specific note for an ID tag.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [ID tag / Note / Delete](https://developers.ampeco.com/reference/idtagnotedelete.md): Delete a specific note from an ID tag.  Notes are permanently deleted.  **Required permission:** `Notes.delete`
- [Installation And Maintenance Companies / Listing](https://developers.ampeco.com/reference/getinstallationandmaintenancecompanieslist.md): Get all Installation And Maintenance Companies
- [Installation And Maintenance Companies / Create](https://developers.ampeco.com/reference/createinstallationandmaintenancecompany.md): Create Installation And Maintenance Company
- [Installation And Maintenance Companies / Read](https://developers.ampeco.com/reference/getinstallationandmaintenancecompany.md): Get Installation And Maintenance Company
- [Installation And Maintenance Companies / Update](https://developers.ampeco.com/reference/updateinstallationandmaintenancecompany.md): Update Installation And Maintenance Company
- [Installation And Maintenance Companies / Delete](https://developers.ampeco.com/reference/deleteinstallationandmaintenancecompany.md): Delete Installation And Maintenance Company
- [InstallerJobs / Listing](https://developers.ampeco.com/reference/getinstallerjobslist.md): Get all Installer Jobs
- [Installer Jobs / Create](https://developers.ampeco.com/reference/createinstallerjob.md): Create Installer Job
- [Installer Jobs / Read](https://developers.ampeco.com/reference/getinstallerjob.md): Get Installer Job
- [Installer Jobs / Update](https://developers.ampeco.com/reference/updateinstallerjob.md): Update Installer Job
- [Installer Jobs / Delete](https://developers.ampeco.com/reference/deleteinstallerjob.md): Delete Installer Job
- [Invoices / Listing](https://developers.ampeco.com/reference/invoiceslisting.md): Get all invoices
- [Invoice / Read](https://developers.ampeco.com/reference/invoiceread.md)
- [Invoice fiscalization attempts / Listing](https://developers.ampeco.com/reference/invoicefiscalizationattemptslisting.md): Get the fiscalization attempts an invoice's integration publishes, newest first. Integrations that do not publish attempts return an empty list.
- [Invoice fiscalization document / Download](https://developers.ampeco.com/reference/invoicefiscalizationdocumentdownload.md): Download one of the document formats the fiscal authority has made available for a fiscalized invoice. Do not construct this URL: follow a `fiscalization.documents[].downloadUrl` link from the invoice response, which already carries the `format`, `expires` and `signature` query parameters. A missing or tampered signature yields `403 Forbidden`. The link expires 24 hours after the invoice response that produced it, after which it yields `410 Gone`, so request the invoice again for a fresh link rather than storing one.  The link is signed and carries its own authorisation — no bearer token is used. The document is fetched from the fiscal authority only when the link is followed, so a provider that cannot supply the format at that moment yields `424 Failed Dependency` rather than a server error.
- [Issues / Listing](https://developers.ampeco.com/reference/issueslisting.md): Get all issues with optional filtering and pagination
- [Issues / Create](https://developers.ampeco.com/reference/issuescreate.md): Create a new issue. Note - auto-resolution statuses (autoRecoveryInProgress, informationCollectionInProgress) cannot be set via API.
- [Issue / Read](https://developers.ampeco.com/reference/issueread.md): Get information for a single issue by ID
- [Issue / Update](https://developers.ampeco.com/reference/issueupdate.md): Update an existing issue. Supports partial updates (PATCH semantics). Notes: - keyResource cannot be updated after creation - Cannot set auto-resolution statuses (autoRecoveryInProgress, informationCollectionInProgress) - When setting status to resolved, wontFix, or nonIssue, resolutionDetails is required
- [Issue / Delete](https://developers.ampeco.com/reference/issuedelete.md): Delete an issue
- [Locations / Listing](https://developers.ampeco.com/reference/locationslistingdeprecated.md): Get all locations
- [Location / Create](https://developers.ampeco.com/reference/locationcreatedeprecated.md): Create new location
- [Location / Read](https://developers.ampeco.com/reference/locationreaddeprecated.md): Get a single location
- [Location / Update](https://developers.ampeco.com/reference/locationupdatedeprecated.md): Update a location
- [Location / Delete](https://developers.ampeco.com/reference/locationdeletedeprecated.md): Delete a location
- [Location / Create](https://developers.ampeco.com/reference/locationcreate.md): Create a new location
- [Locations / Listing](https://developers.ampeco.com/reference/locationslisting.md): Get all locations
- [Location / Update](https://developers.ampeco.com/reference/locationupdate.md): Update a location
- [Location / Read](https://developers.ampeco.com/reference/locationread.md): Get a location
- [Location / Delete](https://developers.ampeco.com/reference/locationdelete.md): Delete a location
- [Location / Charging Zones / Listing](https://developers.ampeco.com/reference/locationchargingzoneslisting.md): Get all Charging Zones
- [Location / Charging Zone / Create](https://developers.ampeco.com/reference/locationchargingzonecreate.md): Create a new Charging Zone
- [Location / Charging Zone / Read](https://developers.ampeco.com/reference/locationchargingzoneread.md): Get a Charging Zone
- [Location / Charging Zones / Update](https://developers.ampeco.com/reference/locationchargingzoneupdate.md): Update a existing Charging Zone
- [Location / Charging Zone / Delete](https://developers.ampeco.com/reference/locationchargingzonedelete.md)
- [Location / Notes / Listing](https://developers.ampeco.com/reference/locationnoteslisting.md): List all notes for a specific location.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [Location / Note / Create](https://developers.ampeco.com/reference/locationnotecreate.md): Create a new note for a specific location.  **Required permission:** `Notes.create`
- [Location / Note / Read](https://developers.ampeco.com/reference/locationnoteshow.md): Get a specific note for a location.  **Required permission:** `Notes.view`
- [Location / Note / Update](https://developers.ampeco.com/reference/locationnoteupdate.md): Update a specific note for a location.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [Location / Note / Delete](https://developers.ampeco.com/reference/locationnotedelete.md): Delete a specific note from a location.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [Operators / Listing](https://developers.ampeco.com/reference/operatorslisting.md): Get all operators the authenticated user has access to
- [Operator / Read](https://developers.ampeco.com/reference/operatorread.md): Get a single operator by ID
- [Parking Space / Create](https://developers.ampeco.com/reference/createparkingspace.md): Create new Parking Space
- [Parking Space / Listing](https://developers.ampeco.com/reference/listparkingspace.md): Get all Parking spaces
- [Parking Space / Update](https://developers.ampeco.com/reference/updateparkingspace.md): Update Parking Space
- [Parking Space / Update](https://developers.ampeco.com/reference/parkingspaceupdate.md): Update a Parking Space
- [Parking Space / Read](https://developers.ampeco.com/reference/getparkingspace.md): Get Parking Space
- [Parking Space / Delete](https://developers.ampeco.com/reference/deleteparkingspace.md): Delete Parking Space
- [Parking Space / EVSEs / Listing](https://developers.ampeco.com/reference/parkingspacesevseslisting.md): Get all EVSEs associated with this parking space.
- [Parking Space / EVSEs / Update](https://developers.ampeco.com/reference/parkingspacesevsessync.md): Sync multiple EVSEs to the Parking Space at once, setting their position and primary status.
- [Partner Contracts / Listing](https://developers.ampeco.com/reference/partnercontractslisting.md): Get all Partner Contracts
- [Partner Contract / Create](https://developers.ampeco.com/reference/partnercontractcreate.md): Create new Partner Contract
- [Partner Contract / Read](https://developers.ampeco.com/reference/partnercontractread.md): Get a Partner Contract
- [Partner Contract / Update](https://developers.ampeco.com/reference/partnercontractupdate.md): Update a Partner Contract
- [Partner Contract / Patch](https://developers.ampeco.com/reference/partnercontractpatch.md): Partially update a Partner Contract. Only provided fields are updated; omitted fields retain their current values.
- [Partner Contract / Delete](https://developers.ampeco.com/reference/partnercontractdelete.md): Delete a Partner Contract
- [Partner invite access policies / listing](https://developers.ampeco.com/reference/partnerinviteaccesspolicieslisting.md): Get all partner invite access policies
- [Partner invite access policy / create](https://developers.ampeco.com/reference/partnerinviteaccesspolicycreate.md): Create a new partner invite access policy
- [Partner invite access policy / read](https://developers.ampeco.com/reference/partnerinviteaccesspolicyread.md): Get a partner invite access policy
- [Partner invite access policy / update](https://developers.ampeco.com/reference/partnerinviteaccesspolicyupdate.md): Update a partner invite access policy. Only provided fields are updated; nested `partnerAccess` and `restrictions` objects are replaced entirely when provided.  Updating `partnerAccess` returns 409 Conflict when the new partner scope would no longer cover partners whose existing invites already reference the policy. Detach those invites or keep those partners in scope first.  The default access policy ("Full private access") cannot be updated.
- [Partner invite access policy / delete](https://developers.ampeco.com/reference/partnerinviteaccesspolicydelete.md): Delete a partner invite access policy. Policies assigned to partner invites cannot be deleted and return a 422 validation error.  The default access policy ("Full private access") cannot be deleted.
- [Partner invite corporate billing policies / Listing](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicieslisting.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get all partner invite corporate billing policies.
- [Partner invite corporate billing policy / Create](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicycreate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Create a partner invite corporate billing policy.
- [Partner invite corporate billing policy / Read](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicyread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single partner invite corporate billing policy.
- [Partner invite corporate billing policy / Update](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicyupdate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Update a partner invite corporate billing policy.
- [Partner invite corporate billing policy / Delete](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicydelete.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Delete a partner invite corporate billing policy. Deletion is rejected while the policy is assigned to pending or accepted partner invites.
- [Partner invite corporate billing policy snapshot / Read](https://developers.ampeco.com/reference/partnerinvitecorporatebillingpolicysnapshotread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single partner invite corporate billing policy snapshot.
- [Partner Invites / Listing](https://developers.ampeco.com/reference/partnerinviteslisting.md): **This endpoint is deprecated. Use `resources/partner-invites/v2.0` instead.**  Get all partner invites
- [Partner Invite / Create](https://developers.ampeco.com/reference/partnerinvitecreate.md): **This endpoint is deprecated. Use `resources/partner-invites/v2.0` instead.**  Create new invite
- [Partner Invite / Read](https://developers.ampeco.com/reference/partnerinviteread.md): **This endpoint is deprecated. Use `resources/partner-invites/v2.0` instead.**  Get a invite
- [Partner Invite / Update](https://developers.ampeco.com/reference/partnerinviteupdate.md): **This endpoint is deprecated. Use `resources/partner-invites/v2.0` instead.**  Update a invite
- [Partner Invite / Delete](https://developers.ampeco.com/reference/partnerinvitedelete.md): **This endpoint is deprecated. Use `resources/partner-invites/v2.0` instead.**  Delete an invite
- [Partner invites / Listing](https://developers.ampeco.com/reference/partnerinviteslistingv2_0.md): Get all partner invites.  **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.
- [Partner invite / Create](https://developers.ampeco.com/reference/partnerinvitecreatev2_0.md): Create a partner invite.  Reimbursement coverage of specific RFIDs and vehicles (`allow`) can be declared here only when the invited email address resolves to an existing user of the partner's operator — the listed RFIDs and vehicles must belong to that user. When no such user exists yet, coverage of specific entities is rejected with a validation error; create the invite without it and declare the covered set via the update endpoint once the invite is accepted.  **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.
- [Partner invite / Read](https://developers.ampeco.com/reference/partnerinvitereadv2_0.md): Get a partner invite.  **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.
- [Partner invite / Update](https://developers.ampeco.com/reference/partnerinviteupdatev2_0.md): Update a partner invite.  **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.
- [Partner invite / Delete](https://developers.ampeco.com/reference/partnerinvitedeletev2_0.md): Delete a partner invite.  **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.
- [Partner Invoices / Listing](https://developers.ampeco.com/reference/partnerinvoiceslisting.md): Get all Partner Invoices visible to the authenticated admin.
- [Partner Invoice / Read](https://developers.ampeco.com/reference/partnerinvoiceread.md): Get a single Partner Invoice including line items and seller/buyer details.
- [Partner Settlement Reports / Listing](https://developers.ampeco.com/reference/partnersettlementreportslisting.md): Get all Partner Settlement Reports
- [Partner Settlement Report / Read](https://developers.ampeco.com/reference/partnersettlementreportread.md): Get a single Partner Settlement Report
- [Partner Settlement Report / Partner Settlement Records / Listing](https://developers.ampeco.com/reference/partnersettlementreportpartnersettlementrecordslisting.md): Get all Partner Settlement Records
- [Partner Settlement Report / Partner Settlement Record / Create](https://developers.ampeco.com/reference/partnersettlementreportpartnersettlementrecordcreate.md): Create Partner Settlement Record
- [Partner Settlement Report / Partner Settlement Record / Read](https://developers.ampeco.com/reference/partnertsettlementreportpartnersettlementrecordread.md): Read Partner Settlement Record
- [Partner Settlement Report / Partner Settlement Record / Update](https://developers.ampeco.com/reference/partnersettlementreportpartnersettlementrecordupdate.md): Update a single Partner Settlement Record
- [Partner Settlement Report / Partner Settlement Record / Delete](https://developers.ampeco.com/reference/partnersettlementreportpartnersettlementrecorddelete.md): Delete a single Partner Settlement Record
- [Partners / Listing](https://developers.ampeco.com/reference/partnerslistingdeprecated.md): Get all partners
- [Partner / Create](https://developers.ampeco.com/reference/partnercreatedeprecated.md): Create new partner
- [Partner / Read](https://developers.ampeco.com/reference/partnerreaddeprecated.md): Get a partner
- [Partner / Update](https://developers.ampeco.com/reference/partnerupdatedeprecated.md): Update a partner
- [Partner / Delete](https://developers.ampeco.com/reference/partnerdeletedeprecated.md): Delete a partner
- [Partners / Listing](https://developers.ampeco.com/reference/partnerslisting.md): Get all partners
- [Partner / Create](https://developers.ampeco.com/reference/partnercreate.md): Create new partner
- [Partner / Read](https://developers.ampeco.com/reference/partnerread.md): Get a partner
- [Partner / Update](https://developers.ampeco.com/reference/partnerupdate.md): Update a partner
- [Partner / Delete](https://developers.ampeco.com/reference/partnerdelete.md): Delete a partner
- [Partner / Admins / Listing](https://developers.ampeco.com/reference/partneradminslisting.md): List all administrators for a specific partner.  Only partner and partnerSiteManager admin types are returned.  **Required permission:** `Admins.view`
- [Partner / Admin / Create](https://developers.ampeco.com/reference/partneradmincreate.md): Create a new administrator for a specific partner.  The administrator type must be either `partner` or `partnerSiteManager`. For `partnerSiteManager`, locationIds is required and must contain valid location IDs owned by the partner.  **Required permission:** `Admins.create`
- [Partner / Admin / Update](https://developers.ampeco.com/reference/partneradminupdate.md): Update an existing partner administrator.  All fields are optional. Only provided fields are updated. For `partnerSiteManager`, locationIds can be updated to change managed locations.  **Required permission:** `Admins.update`
- [Partner / Admin / Delete](https://developers.ampeco.com/reference/partneradmindelete.md): Delete a partner administrator.  Cannot delete yourself (the authenticated admin making the request).  **Required permission:** `Admins.delete`
- [Partner / Notes / Listing](https://developers.ampeco.com/reference/partnernoteslisting.md): List all notes for a specific partner.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [Partner / Note / Create](https://developers.ampeco.com/reference/partnernotecreate.md): Create a new note for a specific partner.  **Required permission:** `Notes.create`
- [Partner / Note / Read](https://developers.ampeco.com/reference/partnernoteshow.md): Get a specific note for a partner.  **Required permission:** `Notes.view`
- [Partner / Note / Update](https://developers.ampeco.com/reference/partnernoteupdate.md): Update a specific note for a partner.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [Partner / Note / Delete](https://developers.ampeco.com/reference/partnernotedelete.md): Delete a specific note from a partner.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [Payment Terminals / Listing](https://developers.ampeco.com/reference/getpaymentterminalsdeprecated.md): **This endpoint is deprecated and will be removed on Tue, 21 Jul 2026.**  Get all payment terminals. Use `/resources/payment-terminals/v1.1` instead.
- [Payment Terminals / Create](https://developers.ampeco.com/reference/createpaymentterminaldeprecated.md): **This endpoint is deprecated and will be removed on Tue, 21 Jul 2026.**  Create a new payment terminal. Use `/resources/payment-terminals/v1.1` instead.
- [Payment Terminals / Read](https://developers.ampeco.com/reference/getpaymentterminaldeprecated.md): **This endpoint is deprecated and will be removed on Tue, 21 Jul 2026.**  Get information for a payment terminal by ID. Use `/resources/payment-terminals/v1.1` instead.
- [Payment Terminals / Update](https://developers.ampeco.com/reference/updatepaymentterminaldeprecated.md): **This endpoint is deprecated and will be removed on Tue, 21 Jul 2026.**  Update payment terminal. Use `/resources/payment-terminals/v1.1` instead.
- [Payment Terminals / Delete](https://developers.ampeco.com/reference/deletepaymentterminaldeprecated.md): **This endpoint is deprecated and will be removed on Tue, 21 Jul 2026.**  Delete a payment terminal. Use `/resources/payment-terminals/v1.1` instead.
- [Payment Terminals / Listing](https://developers.ampeco.com/reference/getpaymentterminalsv1_1.md): Get all payment terminals
- [Payment Terminals / Create](https://developers.ampeco.com/reference/createpaymentterminalv1_1.md): Create a new payment terminal
- [Payment Terminals / Read](https://developers.ampeco.com/reference/getpaymentterminalv1_1.md): Get information for a payment terminal by ID
- [Payment Terminals / Update](https://developers.ampeco.com/reference/updatepaymentterminalv1_1.md): Update Payment terminal
- [Payment Terminals / Delete](https://developers.ampeco.com/reference/deletepaymentterminalv1_1.md): Delete a payment terminal.
- [Provisioning Certificate / Create](https://developers.ampeco.com/reference/createpcid.md): Create Provisioning Certificate
- [Provisioning Certificate / Listing](https://developers.ampeco.com/reference/listpcids.md): Get all Provisioning Certificates
- [Provisioning Certificate / Update](https://developers.ampeco.com/reference/updatepcid.md): Update a Provisioning Certificate
- [Provisioning Certificate / Read](https://developers.ampeco.com/reference/getpcid.md): Get a Provisioning Certificate
- [Provisioning Certificates / Delete](https://developers.ampeco.com/reference/deletepcid.md): Delete a provisioning certificate.
- [Receipts / Listing](https://developers.ampeco.com/reference/receiptslisting.md): Get all receipts
- [Receipt / Read](https://developers.ampeco.com/reference/receiptread.md): Get a single receipt
- [Reimbursement policies / Listing](https://developers.ampeco.com/reference/reimbursementpolicieslisting.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get all reimbursement policies.
- [Reimbursement policy / Create](https://developers.ampeco.com/reference/reimbursementpolicycreate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Create a reimbursement policy.
- [Reimbursement policy / Read](https://developers.ampeco.com/reference/reimbursementpolicyread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single reimbursement policy.
- [Reimbursement policy / Update](https://developers.ampeco.com/reference/reimbursementpolicyupdate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Update a reimbursement policy.
- [Reimbursement policy / Delete](https://developers.ampeco.com/reference/reimbursementpolicydelete.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Delete a reimbursement policy. Deletion is rejected while the policy is attached to partner invites.
- [Reimbursement records / Listing](https://developers.ampeco.com/reference/reimbursementrecordslisting.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get all reimbursement records. A record is one immutable computed reimbursement entry per charging session, including the reversing (credit) records that cancel earlier entries. For the periodic aggregates that group these records per beneficiary, payer and period, use the reimbursement reports listing.
- [Reimbursement record / Read](https://developers.ampeco.com/reference/reimbursementrecordread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single reimbursement record — the immutable computed reimbursement entry for one charging session.
- [Reimbursement reports / Listing](https://developers.ampeco.com/reference/reimbursementreportslisting.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get all reimbursement reports. A report is a periodic aggregate that groups the reimbursement records sharing a beneficiary, payer and period, and exposes their totals. For the per-session entries behind those totals, use the reimbursement records listing.
- [Reimbursement report / Read](https://developers.ampeco.com/reference/reimbursementreportread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single reimbursement report — the periodic aggregate over the reimbursement records sharing a beneficiary, payer and period. The report exposes its aggregated totals; its constituent records can be fetched from the reimbursement records listing via `filter[reportId]`.
- [Reservations / Listing](https://developers.ampeco.com/reference/reservationslisting.md): Get all reservations
- [Reservation / Read](https://developers.ampeco.com/reference/reservationread.md): Get information for a reservation by ID
- [Expenses / Listing](https://developers.ampeco.com/reference/expenseslistingdeprecated.md): Get all expenses
- [Expenses / Listing](https://developers.ampeco.com/reference/expenseslisting.md): This endpoint is deprecated. Use v1.2 for tax-inclusive amount breakdowns.  Get all expenses
- [Expenses / Listing](https://developers.ampeco.com/reference/expensesv1_2listing.md): Get all expenses
- [Revenues / Listing](https://developers.ampeco.com/reference/revenueslistingdeprecated.md): Get all revenues
- [Revenues / Listing](https://developers.ampeco.com/reference/revenueslisting.md): This endpoint is deprecated. Use v1.2 for tax-inclusive amount breakdowns.  Get all revenues
- [Revenues / Listing](https://developers.ampeco.com/reference/revenuesv1_2listing.md): Get all revenues
- [RFID Tags / Listing](https://developers.ampeco.com/reference/rfidtagslistingdeprecated.md): Get all rfid tags
- [RFID Tag / Create](https://developers.ampeco.com/reference/rfidtagcreatedeprecated.md): Create new RFID Tag
- [RFID Tag / Read](https://developers.ampeco.com/reference/rfidtagreaddeprecated.md): Get a RFID Tag
- [RFID Tag / Update](https://developers.ampeco.com/reference/rfidtagupdatedeprecated.md): Update a RFID Tag
- [RFID Tag / Delete](https://developers.ampeco.com/reference/rfidtagdeletedeprecated.md): Delete a RFID Tag
- [Roaming Connections / Listing](https://developers.ampeco.com/reference/listroamingconnections.md): Get all Roaming Connections
- [Roaming Connections / Read](https://developers.ampeco.com/reference/getroamingconnection.md): Get a Roaming Connections
- [Roaming CPOs / Listing](https://developers.ampeco.com/reference/roamingcposlisting.md): Get all Roaming CPOs
- [Roaming CPO / Read](https://developers.ampeco.com/reference/roamingcporead.md): Get a Roaming CPO
- [Roaming CPO / Update](https://developers.ampeco.com/reference/roamingcpoupdate.md): Update Roaming CPO
- [Roaming EMSPs / Listing](https://developers.ampeco.com/reference/roamingemspslisting.md): Get all Roaming EMSPs
- [Roaming EMSP / Create](https://developers.ampeco.com/reference/roamingemspcreate.md): Create new Roaming EMSP  **Only applicable for Hubject OICP, Gireve 2.2.1 and OCPI with missing credentials module emsp roaming connections**
- [Roaming EMSP / Read](https://developers.ampeco.com/reference/roamingemspread.md): Get a Roaming EMSP
- [Roaming EMSP / Update](https://developers.ampeco.com/reference/roamingemspupdate.md): Update Roaming EMSP
- [Roaming EMSP / Delete](https://developers.ampeco.com/reference/roamingemspdelete.md): Delete a Roaming EMSP
- [Roaming EMSP Partners / Listing](https://developers.ampeco.com/reference/roamingemsppartnerslisting.md): List the partner assigned to this Roaming EMSP for each platform operator. `partnerId` is `null` when no partner is assigned. Use `POST /actions/roaming-emsp/v1.0/{roamingEmsp}/assign-partner` to assign or clear a partner.
- [Roaming Operators / Listing](https://developers.ampeco.com/reference/roamingoperatorslisting.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-cpos/v1.0` instead. Get all Roaming Operators
- [Roaming Operator / Read](https://developers.ampeco.com/reference/roamingoperatorread.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-cpos/v1.0/{roamingCpo}` instead. Get a Roaming Operator
- [Roaming Operator / Update](https://developers.ampeco.com/reference/roamingoperatorupdate.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-cpos/v1.0/{roamingCpo}` instead. Update Roaming Operator
- [Roaming Operators / Custom Tariff Filters / Listing](https://developers.ampeco.com/reference/listroamingcustomtarifffilters.md): Get all custom tariff filters for a roaming operator
- [Roaming Operators / Custom Tariff Filters / Create](https://developers.ampeco.com/reference/createroamingcustomtarifffilter.md): Create new custom tariff filter for a roaming operator
- [Roaming Operators / Custom Tariff Filters / Reorder](https://developers.ampeco.com/reference/reorderroamingcustomtarifffilters.md): Change the ordering of custom tariff filters for a roaming operator. This operation allows partial reordering - you only need to specify the filters that need to move. Filters not included in the request will maintain their relative positions. The atomic operation prevents inconsistent states during reordering.
- [Roaming Operators / Custom Tariff Filters / Read](https://developers.ampeco.com/reference/getroamingcustomtarifffilter.md): Get a specific custom tariff filter
- [Roaming Operators / Custom Tariff Filters / Update](https://developers.ampeco.com/reference/updateroamingcustomtarifffilter.md): Update an existing custom tariff filter
- [Roaming Operators / Custom Tariff Filters / Delete](https://developers.ampeco.com/reference/deleteroamingcustomtarifffilter.md): Delete a custom tariff filter
- [Roaming Platforms / Listing](https://developers.ampeco.com/reference/roamingplatformslistingdeprecated.md): Get all Roaming Platforms. See Roaming Connections for the list of supported protocols.
- [Roaming Platform / Read](https://developers.ampeco.com/reference/roamingplatformreaddeprecated.md): Get a Roaming Platform. See Roaming Connections for the list of supported protocols.
- [Roaming Providers / Listing](https://developers.ampeco.com/reference/roamingproviderslisting.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-emsps/v1.0` instead. Get all Roaming Providers
- [Roaming Provider / Create](https://developers.ampeco.com/reference/roamingprovidercreate.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-emsps/v1.0` instead. Create new Roaming Provider  **Only applicable for Hubject, Gireve 2.2.1 and OCPI with missing credentials module emsp roaming connections**
- [Roaming Provider / Read](https://developers.ampeco.com/reference/roamingproviderread.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-emsps/v1.0/{roamingEmsp}` instead. Get a Roaming Provider
- [Roaming Provider / Update](https://developers.ampeco.com/reference/roamingproviderupdate.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-emsps/v1.0/{roamingEmsp}` instead. Update Roaming Providers
- [Roaming Provider / Delete](https://developers.ampeco.com/reference/roamingproviderdelete.md): **This endpoint is deprecated and will be removed on Fri, 30 Oct 2026.**  Use `/resources/roaming-emsps/v1.0/{roamingEmsp}` instead. Delete a Roaming Provider
- [Roaming Tariffs / Listing](https://developers.ampeco.com/reference/roamingtariffslisting.md): Get all Roaming Tariffs
- [Roaming Tariff / Read](https://developers.ampeco.com/reference/roamingtariffread.md): Get a Roaming Tariff
- [Roaming Tariff / Update](https://developers.ampeco.com/reference/roamingtariffupdate.md): Update Roaming Tariff
- [Security Events Logs / Listing](https://developers.ampeco.com/reference/securityeventlogslistingdeprecated.md): Get all Security Events Log
- [Security Event Log / Read](https://developers.ampeco.com/reference/securityeventlogreaddeprecated.md): Get a Security Event Log
- [Security Events / Listing](https://developers.ampeco.com/reference/securityeventslisting.md): Get all Security Events
- [Security Event / Read](https://developers.ampeco.com/reference/securityeventread.md): Get a Security Event
- [Sessions / Listing](https://developers.ampeco.com/reference/sessionslisting.md)
- [Session / Read](https://developers.ampeco.com/reference/sessionread.md)
- [Session / update custom fields](https://developers.ampeco.com/reference/sessionupdate.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Update the applicable custom field values of a session without changing any other session properties.
- [Sessions / Consumption Stats / Read](https://developers.ampeco.com/reference/sessionsconsumptionstatsread.md): Consumption statistics may differ between active and finished sessions, as finished sessions display aggregated final data with a maximum of 300 items.
- [Session / Energy coupon session consumptions](https://developers.ampeco.com/reference/energycouponsessionconsumptionslisting.md): List the energy coupons consumed during a charging session, with the energy consumed from each.
- [Sessions / Timeline Snapshot / Read](https://developers.ampeco.com/reference/sessiontimelinesnapshotread.md): Returns the meter value time-series and lifecycle events for a finished charging session.  **Availability.** Snapshots are generated when a session completes. Active sessions return 404. Finished sessions without snapshots, including sessions that finished before snapshot generation was available, also return 404. There is no historical backfill.  **For active sessions**, use `GET /logs/communication/v1.0?filter[sessionId]={id}&filter[command]=MeterValues` to read real-time OCPP meter values from communication logs (6-month retention).
- [Settings / Listing](https://developers.ampeco.com/reference/settingslisting.md): Get all settings
- [Sharing invites / Listing](https://developers.ampeco.com/reference/sharinginviteslisting.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get all sharing invites. A sharing invite represents a personal charge point owner sharing their charge point with another user.
- [Sharing invite / Read](https://developers.ampeco.com/reference/sharinginviteread.md): ⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.  Get a single sharing invite.
- [Sub operators / Listing](https://developers.ampeco.com/reference/suboperatorslistingdeprecated.md): **Deprecated.** Use v2.0 endpoint instead for enhanced functionality.
- [Sub operator / Read](https://developers.ampeco.com/reference/suboperatorreaddeprecated.md): **Deprecated.** Use v2.0 endpoint instead for enhanced functionality.
- [Sub-operators / Listing](https://developers.ampeco.com/reference/suboperatorslisting.md): Get all sub-operators. Returns sub-operators ordered by businessName ascending by default. Uses cursor-based pagination.
- [Sub-operators / Create](https://developers.ampeco.com/reference/suboperatorcreate.md): Create a new sub-operator
- [Sub-operators / Read](https://developers.ampeco.com/reference/suboperatorread.md): Get a single sub-operator
- [Sub-operators / Update](https://developers.ampeco.com/reference/suboperatorupdate.md): Update an existing sub-operator. Only provided fields are updated - omitted fields retain their current values. Send null for nullable fields to explicitly clear their values.
- [Sub-operators / Delete](https://developers.ampeco.com/reference/suboperatordelete.md): Permanently delete a sub-operator. When deleted, associated partners are unassociated but remain intact. All admin accounts belonging to this sub-operator are also deleted.
- [Sub Operator / Notes / Listing](https://developers.ampeco.com/reference/suboperatornoteslisting.md): List all notes for a specific sub-operator.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [Sub Operator / Note / Create](https://developers.ampeco.com/reference/suboperatornotecreate.md): Create a new note for a specific sub-operator.  **Required permission:** `Notes.create`
- [Sub Operator / Note / Read](https://developers.ampeco.com/reference/suboperatornoteshow.md): Get a specific note for a sub-operator.  **Required permission:** `Notes.view`
- [Sub Operator / Note / Update](https://developers.ampeco.com/reference/suboperatornoteupdate.md): Update a specific note for a sub-operator.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [Sub Operator / Note / Delete](https://developers.ampeco.com/reference/suboperatornotedelete.md): Delete a specific note from a sub-operator.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [Subscription Plans / Listing](https://developers.ampeco.com/reference/subscriptionplanslistingdeprecated.md): Get all Subscription Plans
- [Subscription plans / Listing](https://developers.ampeco.com/reference/subscriptionplanslisting.md): Get all Subscription plans
- [Subscription plan / Create](https://developers.ampeco.com/reference/subscriptionplancreate.md): Create a new Subscription plans
- [Subscription plan / Read](https://developers.ampeco.com/reference/subscriptionplanread.md): Get a single subscription plan
- [Subscription plan / Update](https://developers.ampeco.com/reference/subscriptionplanupdate.md): Update a Subscription plan
- [Subscription plan / Delete](https://developers.ampeco.com/reference/subscriptionplandelete.md): Delete a Subscription plan
- [Subscriptions / Listing](https://developers.ampeco.com/reference/subscriptionslisting.md): Get all subscriptions
- [Subscription / Read](https://developers.ampeco.com/reference/subscriptionread.md): Get a single subscription
- [Tariff Groups / Listing](https://developers.ampeco.com/reference/tariffgroupslisting.md): Get all tariff groups
- [Tariff Group / Create](https://developers.ampeco.com/reference/tariffgroupcreate.md): Create new tariff group. When the tariff group is created a base tariff is also created. The type of the base tariff (free or charging not allowed) is determined by the respective setting of the operator.
- [Tariff Group / Read](https://developers.ampeco.com/reference/tariffgroupread.md): Get a tariff group
- [Tariff Group / Update](https://developers.ampeco.com/reference/tariffgroupupdate.md): Update a tariff group
- [Tariff Group / Delete](https://developers.ampeco.com/reference/tariffgroupdelete.md): Delete a tariff group.  **Deletion limitations**  A tariff group cannot be deleted when either of the following is true: - Charge points are assigned to it — at least one EVSE currently references the tariff group. - It is the operator's default tariff group — the tariff group is marked as the default for the operator.  Both conditions must be false for the deletion to succeed.
- [Tariff Snapshot / Read](https://developers.ampeco.com/reference/tariffsnapshotread.md): Get a tariff snapshot by id
- [Tariffs / Listing](https://developers.ampeco.com/reference/tariffslisting.md): Get all tariff. Also you could use the `tariffGroupId` and the `userId` to "resolve" the concrete tariff within a group that would be applied to the specified user.
- [Tariff / Create](https://developers.ampeco.com/reference/tariffcreate.md): Create new tariff
- [Tariff / Read](https://developers.ampeco.com/reference/tariffread.md): Get a tariff
- [Tariff / Update](https://developers.ampeco.com/reference/tariffupdate.md): Update a tariff
- [Tariff / Partial Update](https://developers.ampeco.com/reference/tariffpartialupdate.md): Partially update a tariff. Only the fields included in the request body are updated. Omitted fields retain their current values. Nested objects are merged recursively, while arrays are fully replaced. The tariff type cannot be changed via PATCH — use PUT with the full payload instead.
- [Tariff / Delete](https://developers.ampeco.com/reference/tariffdelete.md): Delete a tariff
- [Tariff / Scheduled Changes / Listing](https://developers.ampeco.com/reference/tariffscheduledchangeslisting.md): Get all scheduled pricing changes for a tariff
- [Tariff / Scheduled Change / Create](https://developers.ampeco.com/reference/tariffscheduledchangecreate.md): Create a new scheduled pricing change for the tariff
- [Tariff / Scheduled Change / Delete](https://developers.ampeco.com/reference/tariffscheduledchangedelete.md): Delete a scheduled pricing change
- [Tariff / Scheduled Change / Read](https://developers.ampeco.com/reference/tariffscheduledchangeread.md): Get a single scheduled pricing change
- [Tariff / Scheduled Change / Update](https://developers.ampeco.com/reference/tariffscheduledchangeupdate.md): Update a pending scheduled pricing change
- [Tax Identification Numbers / Listing](https://developers.ampeco.com/reference/taxidentificationnumberslisting.md): Get all Tax Identification Numbers
- [Tax Identification Number / Create](https://developers.ampeco.com/reference/taxidentificationnumbercreate.md): Create new Tax Identification Number
- [Tax Identification Number / Read](https://developers.ampeco.com/reference/taxidentificationnumberread.md): Get a Tax Identification Number
- [Tax Identification Number / Update](https://developers.ampeco.com/reference/taxidentificationnumberupdate.md): Tax Identification Numbers
- [Tax Identification Number / Delete](https://developers.ampeco.com/reference/taxidentificationnumberdelete.md): Delete a Tax Identification Number
- [Taxes / Listing](https://developers.ampeco.com/reference/taxeslisting.md): Get all Taxes
- [Tax / Create](https://developers.ampeco.com/reference/taxcreate.md): Create new Tax
- [Tax / Read](https://developers.ampeco.com/reference/taxread.md): Get a Tax
- [Tax / Update](https://developers.ampeco.com/reference/taxupdate.md): Taxes
- [Tax / Delete](https://developers.ampeco.com/reference/taxdelete.md): Delete a Tax
- [Templates / Listing](https://developers.ampeco.com/reference/templateslisting.md): Get all charge points templates
- [Terms and policies / Listing](https://developers.ampeco.com/reference/termsandpolicieslisting.md)
- [Terms and policies / Read](https://developers.ampeco.com/reference/termsandpoliciesread.md)
- [Top-Up Packages / Listing](https://developers.ampeco.com/reference/topuppackageslisting.md): Get all Top-Up Packages
- [Top-Up Package / Create](https://developers.ampeco.com/reference/topuppackagcreate.md): Create new Top-Up Package
- [Top-Up Package / Read](https://developers.ampeco.com/reference/topuppackageread.md): Get a Top-Up Package
- [Top-Up Package / Update](https://developers.ampeco.com/reference/topuppackageupdate.md): Top-Up Packages
- [Top-Up Package / Delete](https://developers.ampeco.com/reference/topuppackagedelete.md): Delete a Top-Up Package
- [Transactions / Listing](https://developers.ampeco.com/reference/transactionslisting.md): Get all transactions
- [Transactions / Create](https://developers.ampeco.com/reference/transactionscreate.md): Create new Transaction
- [Transaction / Read](https://developers.ampeco.com/reference/transactionread.md): Get a transation
- [Transaction / Update](https://developers.ampeco.com/reference/transactionupdate.md): Update a non-finalised transaction
- [User devices / Listing](https://developers.ampeco.com/reference/userdeviceslisting.md): Get a list of user devices registered by the mobile app.  Devices are created when the mobile app first communicates with the platform. A user can have multiple devices (one per device where they are logged in). The association is removed on logout — the device record persists with no associated user (an "orphaned" device).  **Operator scoping:** For operator-scoped tokens, only devices currently associated with a user belonging to the token's operator are returned. Orphaned devices are excluded because the operator that registered the device is no longer resolvable after logout. Devices whose associated user has been soft-deleted ARE returned for the operator they belonged to — the soft-deleted-user signal is preserved for fraud-detection workflows. Applying `filter[operatorId]` follows the same rule.  Results are paginated using cursor-based pagination. By default they are ordered by device ID descending (newest devices first); use the `sort` parameter to override this order.
- [User device / Read](https://developers.ampeco.com/reference/userdeviceread.md): Get a single user device by ID.  **Operator scoping:** Operator-scoped tokens can only read devices currently associated with a user belonging to the token's operator. Devices outside this scope — including orphaned devices — return 404 (the existence of the device is not leaked). Devices whose associated user has been soft-deleted ARE returned to operator-scoped tokens when the soft-deleted user belonged to the token's operator.
- [User Groups / Listing](https://developers.ampeco.com/reference/usergroupslisting.md): Get all user groups
- [User Group / Create](https://developers.ampeco.com/reference/usergroupcreate.md): Create new user group.
- [User Group / Read](https://developers.ampeco.com/reference/usergroupread.md): Get an user group
- [User Group / Update](https://developers.ampeco.com/reference/usergroupupdate.md): Update a user group
- [User Group / Delete](https://developers.ampeco.com/reference/usergroupdelete.md): Delete a user group
- [Users / Listing](https://developers.ampeco.com/reference/userslisting.md): Get all users
- [User / Create](https://developers.ampeco.com/reference/usercreate.md): Create new User
- [User / Read](https://developers.ampeco.com/reference/userread.md): Get a user
- [User / Update](https://developers.ampeco.com/reference/userupdate.md): Update user
- [User / Delete](https://developers.ampeco.com/reference/userdelete.md): Delete a user
- [Invoice details / Read](https://developers.ampeco.com/reference/invoicedetailsread.md)
- [Invoice details / Create or update](https://developers.ampeco.com/reference/invoicedetailscreateorupdate.md): Create or update user invoice details.  **Important**: When the operator has "Always collect Invoice Details" enabled in their invoice integration settings, the `requireInvoice` field will always be set to `true` regardless of the request payload value. This override ensures regulatory compliance and business policy enforcement. No error is returned when overrides occur as this is intentional behavior.
- [Payment Methods / Listing](https://developers.ampeco.com/reference/paymentmethodslisting.md): Get all payment methods for a user
- [Payment Method / Create](https://developers.ampeco.com/reference/paymentmethodcreate.md): Initiate a new payment method registration, or finalize it.   Note that this is a two step process!  # For payment processors with web view integration   You will need to initiate a call with no parameters to this endpoint to get a new request to add payment method (Step 1). Then you will have to redirect to an endpoint and wait for the client to enter his credit card details there. Once he/she is done (and reaches the successURL) you must then issue another call to this endpoint with the transactionID that was returned from the first call to finalize the process and retrieve the newly added payment method data (Step 2).   ## Step 1  POST with request body, containing `tokenizedType` to determine the type of the method and `bankTransferType` if applicable.   This will create a new request to the payment processor for adding a new payment method. As response you will get the `transactionId` to track the payment method registration process, the `redirectUrl` and `successUrl`, to redirect your user to, along with any other attributes that the payment processor requires for tracking. Just pass those additional parameters to Step 2.  ### Example request for tokenizedType = card Request: ```json {   "tokenizedType": "card" } ```  ### Example request for tokenizedType = bank_transfer Request: ```json {   "tokenizedType": "bank_transfer",   "bankTransferType": "sepa" } ```  Response: ```json {   "transactionId": 1234,   "successUrl": "http://example.com/payment-processor/success",   "redirectUrl": "http://example.com/payment-processor/web-form/123abc",   "additionalProcessorArguments": "just pass them all top the step 2" } ```   ## Step 2  POST with request body, containing the `transactionId` along with any other attributes, that were in the response of Step 1 (other then the `transactionId`, `successUrl` and `redirectUrl`).   This will finalize the payment method registration and will retrieve the newly added payment method for you. Note that you can also receive the payment methods using the payment methods listing endpoints.  ### Example Request: ```json {   "transactionId": 1234,   "successUrl": "http://example.com/payment-processor/success",   "redirectUrl": "http://example.com/payment-processor/web-form/123abc",   "additionalProcessorArguments": "just pass them all top the step 2" } ``` Response for card: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "card",     "issuer": "visa",     "cardNetwork": "visa",     "cardType": "credit",     "bin": "411111",     "fingerprint": "CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5",     "acquirerName": "Worldline",     "expireYear": 2026,     "expireMonth": 5,     "default": true,   } } ``` Response for bank transfer: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "bank_transfer",     "bankTransferType": "sepa",     "issuer": null,     "expireYear": null,     "expireMonth": null,     "default": true,   } } ```   # For payment processors with in-app integration   Braintree and Stripe integrations DO NOT count out `redirectUrl` as these processors should have an ip-app integration and therefore the app itself should use the appropriate SDK to complete the credit-card tokenization process with the processor.  ## Braintree The first step is not required for braintree as the full integration is done in-app. Step 2 needs to pass the `paymentMethodNonce` so that it can be exchanged for the payment method token.  ### Example Step 2 Request: ```json {"paymentMethodNonce": "abc123"} ``` Response for card: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "card",     "issuer": "visa",     "cardNetwork": "visa",     "cardType": "credit",     "bin": "411111",     "fingerprint": "CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5",     "acquirerName": "Worldline",     "expireYear": 2026,     "expireMonth": 5,     "default": true,   } } ``` Response for bank transfer: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "bank_transfer",     "bankTransferType": "sepa",     "issuer": null,     "expireYear": null,     "expireMonth": null,     "default": true,   } } ```  ## Stripe Step 1 with stripe will initialize a setup intent, that your app should complete. You will get the details you need in order to do that from the response of that call. Call step 2 once you have completed the setup intent.  ### Example Step 1 - when tokenizing card ```json {   "tokenizedType": "card" } ```  ### Example Step 1 - when tokenizing bank transfer Request: ```json {   "tokenizedType": "bank_transfer",   "bankTransferType": "sepa" } ```  Response: ```json {   "publishableKey": "345678986543",   "clientSecret": "jyt37hgsv63",   "setupIntentReference": "1234ABC" } ```  ### Example Step 2 Request: ```json {   "publishableKey": "345678986543",   "clientSecret": "jyt37hgsv63",   "setupIntentReference": "1234ABC" } ``` Response for card: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "card",     "issuer": "visa",     "cardNetwork": "visa",     "cardType": "credit",     "bin": "411111",     "fingerprint": "CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5",     "acquirerName": "Worldline",     "expireYear": 2026,     "expireMonth": 5,     "default": true,   } } ``` Response for bank transfer: ```json {   "data": {     "id": 1234,     "name": "**** 1111",     "type": "tokenized",     "tokenizedType": "bank_transfer",     "bankTransferType": "sepa",     "issuer": null,     "expireYear": null,     "expireMonth": null,     "default": true,   } } ```
- [Payment Method / Read](https://developers.ampeco.com/reference/paymentmethodread.md): Get information for a payment method by ID
- [Payment Method / Update](https://developers.ampeco.com/reference/paymentmethodupdate.md): Update Payment method. Please note that `balance` and `corporate` payment methods CANNOT be set as default
- [Payment Method / Delete](https://developers.ampeco.com/reference/paymentmethoddelete.md): Delete Payment method. Please note that `balance` and `corporate` payment methods CANNOT be removed from this interface
- [Subscription billing periods / Listing](https://developers.ampeco.com/reference/subscriptionbillingperiodslisting.md): Get all subscription billing periods for a user
- [Subscription billing period / Read](https://developers.ampeco.com/reference/subscriptionbillingperiodread.md): Get information for a subscription billing period by ID
- [Users / Listing](https://developers.ampeco.com/reference/userslistingv1_1.md): Get all users
- [User / Create](https://developers.ampeco.com/reference/usercreatev1_1.md): Create new User
- [User / Read](https://developers.ampeco.com/reference/userreadv1_1.md): Get a user
- [User / Update](https://developers.ampeco.com/reference/userupdatev1_1.md): Update user
- [User / Delete](https://developers.ampeco.com/reference/userdeletev1_1.md): Delete a user
- [User / Notes / Listing](https://developers.ampeco.com/reference/usernoteslisting.md): List all notes for a specific user.  Notes are returned with pinned notes first, then ordered by creation date descending.  **Required permission:** `Notes.view`
- [User / Note / Create](https://developers.ampeco.com/reference/usernotecreate.md): Create a new note for a specific user.  **Required permission:** `Notes.create`
- [User / Note / Read](https://developers.ampeco.com/reference/usernoteshow.md): Get a specific note for a user.  **Required permission:** `Notes.view`
- [User / Note / Update](https://developers.ampeco.com/reference/usernoteupdate.md): Update a specific note for a user.  **Required permissions:** - `Notes.update` for updating summary and details - `Notes.pin` for updating the pinned field (in addition to Notes.update if other fields are included)
- [User / Note / Delete](https://developers.ampeco.com/reference/usernotedelete.md): Delete a specific note from a user.  Notes are permanently deleted (hard delete).  **Required permission:** `Notes.delete`
- [Utilities / Listing](https://developers.ampeco.com/reference/listutilities.md): Get all Utilities
- [Utilities / Create](https://developers.ampeco.com/reference/createutility.md): Create Utility
- [Utilities / Read](https://developers.ampeco.com/reference/getutility.md): Get a single Utility
- [Utilities / Update](https://developers.ampeco.com/reference/updateutility.md): Update a single Utility
- [Utilities / Delete](https://developers.ampeco.com/reference/deleteutility.md): Delete a single Utility
- [Vehicles / Listing](https://developers.ampeco.com/reference/vehicleslisting.md): Get a list of vehicles.
- [Vehicle / Create](https://developers.ampeco.com/reference/vehiclecreate.md): Create a new vehicle.
- [Vehicle telemetry readings / listing](https://developers.ampeco.com/reference/vehicletelemetryreadingslisting.md): Get a list of vehicle telemetry readings.
- [Vehicle / Read](https://developers.ampeco.com/reference/vehicleread.md): Get a vehicle by ID.
- [Vehicle / Update](https://developers.ampeco.com/reference/vehicleupdate.md): Update a vehicle.
- [Vehicle / Delete](https://developers.ampeco.com/reference/vehicledelete.md): Delete a vehicle.
- [Vehicle / Users / Listing](https://developers.ampeco.com/reference/vehicleuserslisting.md): List the IDs of the users currently assigned to the vehicle.
- [Vehicle / Users / Replace](https://developers.ampeco.com/reference/vehicleusersreplace.md): Replace the full set of users assigned to the vehicle.  Pass `{ "userIds": [...] }` with the complete desired assignment. Sending `[]` detaches every user. The response returns the post-operation user ID list.
- [Vehicle / Users / Attach](https://developers.ampeco.com/reference/vehicleusersattach.md): Attach one or more users to the vehicle.  Idempotent — attaching a user that is already assigned is a silent no-op. The response returns the post-operation user ID list.
- [Vehicle / Users / Detach](https://developers.ampeco.com/reference/vehicleusersdetach.md): Detach a single user from the vehicle.  Returns the post-operation user ID list. Detaching a user that is not currently assigned returns `404`.
- [Vehicle telemetry readings / Listing](https://developers.ampeco.com/reference/vehicletelemetryreadingsbyvehiclelisting.md): List telemetry readings for a vehicle, ordered by submission time descending.
- [Vehicle telemetry reading / Create](https://developers.ampeco.com/reference/vehicletelemetryreadingcreate.md): Submit a new telemetry reading for a vehicle.
- [Vehicle telemetry reading / Delete](https://developers.ampeco.com/reference/vehicletelemetryreadingdelete.md): Delete an erroneous telemetry reading.
- [Vendor Error Codes / Listing](https://developers.ampeco.com/reference/vendorerrorcodeslisting.md): Get all Vendor Error Codes
- [Vendor Error Code / Create](https://developers.ampeco.com/reference/vendorerrorcodecreate.md): Create new Vendor Error Code
- [Vendor Error Code / Read](https://developers.ampeco.com/reference/vendorerrorcoderead.md): Get a Vendor Error Code
- [Vendor Error Code / Update](https://developers.ampeco.com/reference/vendorerrorcodeupdate.md): Vendor Error Code
- [Vendor Error Code / Delete](https://developers.ampeco.com/reference/vendorerrorcodedelete.md): Delete a Vendor Error Code
- [Vouchers / Listing](https://developers.ampeco.com/reference/voucherslistingdeprecated.md): Get all Vouchers
- [Voucher / Create](https://developers.ampeco.com/reference/vouchercreatedeprecated.md): Create new Voucher
- [Voucher / Read](https://developers.ampeco.com/reference/voucherreaddeprecated.md): Get a Voucher
- [Voucher / Update](https://developers.ampeco.com/reference/voucherupdatedeprecated.md): Update a Voucher
- [Voucher / Delete](https://developers.ampeco.com/reference/voucherdeletedeprecated.md): Delete a Voucher
- [Vouchers / Listing](https://developers.ampeco.com/reference/voucherslisting.md): Get all Vouchers
- [Voucher / Create](https://developers.ampeco.com/reference/vouchercreate.md): Create new Voucher
- [Voucher / Read](https://developers.ampeco.com/reference/voucherread.md): Get a Voucher
- [Voucher / Update](https://developers.ampeco.com/reference/voucherupdate.md): Update a Voucher
- [Voucher / Delete](https://developers.ampeco.com/reference/voucherdelete.md): Delete a Voucher

## Changelog
- [3.244.0 release notes](https://developers.ampeco.com/changelog/32440-release-notes.md)
- [3.243.0 release notes](https://developers.ampeco.com/changelog/32430-release-notes.md)
- [3.242.0 release notes](https://developers.ampeco.com/changelog/32420-release-notes.md)
- [3.240.0 release notes](https://developers.ampeco.com/changelog/32400-release-notes.md)
- [3.239.0 release notes](https://developers.ampeco.com/changelog/32390-release-notes.md)
- [3.238.0 release notes](https://developers.ampeco.com/changelog/32380-release-notes.md)
- [3.237.0 release notes](https://developers.ampeco.com/changelog/32370-release-notes.md)
- [3.236.0 release notes](https://developers.ampeco.com/changelog/32360-release-notes.md)
- [3.235.0 release notes](https://developers.ampeco.com/changelog/32350-release-notes.md)
- [3.234.0 release notes](https://developers.ampeco.com/changelog/32340-release-notes.md)