Version 2026-1, effective 9 July 2026
Issued by Volt Time B.V., trading as Plugchoice (KvK 77488873, De Entree 99, 1101 HE Amsterdam, support@plugchoice.com). These terms supplement the Plugchoice General Terms; in case of conflict these terms prevail for API use. "Developer" means the party accessing the API.
1. Access tiers
1.1. Personal Access Tokens (free): for the account holder's own personal, non-commercial use (home automation, personal dashboards, testing). Any commercial use, use in a product or service offered to others, or access to data of accounts other than your own requires API Professional.
1.2. API Professional (OAuth 2.0): for production integrations, under a separate agreement covering scopes, rate limits and fees. Users connect their Plugchoice account to the Developer's application through the OAuth consent flow and can revoke at any time.
1.3. We may verify use and reclassify accounts that use free tokens commercially.
2. User consent and data
2.1. The Developer may access user data only within the scopes the user granted, and may use it solely to provide its own service to that user. Reselling, brokering, enriching third-party datasets, or advertising profiles based on API data is prohibited.
2.2. Upon revocation of a connection or deletion of the user's account, the Developer deletes the personal data obtained through the API without undue delay, except where the Developer must retain it under its own legal obligations.
2.3. For personal data received through the API, the Developer is an independent controller and is responsible for its own lawful basis, transparency and data subject rights.
2.4. ERE booking service providers: session data (including meter values and EAN-related data) is provided exclusively for registration, verification and booking of emission reduction units for the authorizing user, and may not be used for marketing or any other purpose.
3. Acceptable use
3.1. The Developer may not: (a) clone the Platform or build a competing charge point management system using the API or data obtained through it; (b) benchmark or publish performance comparisons without our written consent; (c) resell or sublicense API access; (d) bulk-extract data beyond the connected users' own data or circumvent pagination, scopes or rate limits; (e) probe, scan or test vulnerabilities except under our Responsible Disclosure policy; (f) misrepresent its application's identity or purpose in the consent flow; (g) automate ownership transfers, sensitive-access grants or other consent-type actions on behalf of users without an explicit, informed, per-action confirmation by the user in the Developer's application.
3.2. Rate limits apply per tier. We may throttle, restrict or block traffic that endangers the Platform, without notice where reasonably necessary.
4. Commands that affect physical equipment
4.1. Endpoints that start, stop, restart, reconfigure or update Chargers (including Bulk Command, charging profiles, firmware and lock controls) affect real electrical equipment. The Developer is responsible for every command issued with its credentials or tokens, including commands triggered automatically by its application.
4.2. The Developer must implement safeguards proportionate to its use (confirmation steps, sane defaults, kill switches for automation) and must not issue bulk or destructive commands to Chargers of users who have not clearly enabled that functionality in the Developer's application.
4.3. General Terms clauses 6 (steering, at own risk), 7 (data accuracy) and 9 (firmware) apply in full to API use.
4a. Data accuracy
4a.1. All data available through the API originates from Chargers, from user input, or from our own records (including compatibility and meter certification designations such as MID status). It is provided as-is, may contain errors, and is not warranted accurate or fit for billing, reimbursement, certification or other purposes with financial or legal consequences.
4a.2. The Developer must not present such data to its users as verified or certified, and must verify certification-dependent attributes independently before building financial flows (such as reimbursement or ERE booking) on them.
5. Payments, reimbursement and wallet endpoints
5.1. Endpoints relating to billing, reimbursement, payouts, payment methods and public charging (including any wallet functionality) are available only where we have enabled them for the Developer or the underlying account, and are subject to General Terms Schedule B, including its phased-rollout regime, and to the requirements of our payment provider.
5.2. The Developer may not store or transmit full payment credentials outside the payment provider's mechanisms.
6. Availability, versioning and changes
6.1. The API is provided as-is, without uptime or support commitments unless agreed in writing. Endpoints marked beta carry no commitments at all.
6.2. We may add, change, deprecate or remove endpoints and fields. For API Professional we aim to give reasonable advance notice of breaking changes; for free tokens no notice is owed.
6.3. We may suspend or terminate API access with immediate effect for breach of these terms, security risk, or abuse; otherwise clauses 14 and 15 of the General Terms apply.
7. Security and incidents
7.1. The Developer keeps tokens, keys and secrets confidential, uses them only server-side where the tier requires it, and rotates them on suspicion of compromise.
7.2. The Developer informs us at support@plugchoice.com without undue delay, and at the latest within 48 hours, after discovering a security incident involving API credentials or data obtained through the API.
8. Liability and indemnity
8.1. The liability regime of the General Terms (clause 12) applies. In addition, the Developer indemnifies us against third-party claims arising from the Developer's application, its use of the API, its commands to Chargers, or its processing of data obtained through the API.
9. Intellectual property
9.1. The API, documentation and all Platform data remain ours or our licensors'. The Developer receives a non-exclusive, non-transferable, revocable right to access the API per these terms. Feedback may be used by us freely.
9.2. The Developer may state that its application "works with Plugchoice" but may not use our name or logo in a way that suggests endorsement without written consent.
10. Miscellaneous
10.1. We may amend these terms per clause 14 of the General Terms. Dutch law applies; exclusive forum is the competent court of The Hague.