API and Developer Terms
Version 2026-2, published 2026-10-30. It applies to accounts created from 2026-10-30 and to existing accounts from 2026-11-30.
Issued by Volt Time B.V. (KvK 77488873), also trading as Plugchoice. These terms add to our General Terms ("GT"). The Definitions, version 2026-2, at plugchoice.com/legal/definitions, form part of these terms. "API Data" is data obtained through the API and information derived from it. Whoever accesses the API, also with another person's token or account, accepts these terms and the GT by doing so.
1. Access tiers
1.1. Personal Access Tokens are for the user's own use of its own account. Any other use ("Commercial Use"), such as use in a product or service for others or access to other accounts' data, also by or for another party with the user's token or account, requires API Professional; under the EU Data Act, access for another party is making data available to that party (articles 5 and 9). The Customer and the provider it switches to may use the API for a switch under GT 15.5, free of charge where the EU Data Act requires it; that use is not Commercial Use. We may change, limit, charge for or end Personal Access Tokens under GT 14.
1.2. API Professional (OAuth 2.0): for production integrations, under a separate agreement on scopes, limits and fees.
1.3. Partner exchange: reciprocal API access on the terms of a signed individual agreement.
1.4. If free access is put to Commercial Use without a signed individual agreement with us, we may reclassify the account; invoice that use from its start to whoever uses it, never to a Consumer, at our fees for comparable use or else a reasonable fee, with statutory commercial interest; and require API Professional or an end to that use.
2. User consent and data
2.1. The Developer uses user data only within the scopes the user granted and for its own service to that user. Passing API Data, or the ability to steer a Charger, to another party requires a signed individual agreement with us allowing it and the user's choice of that use.
2.2. When a connection is revoked, the user's account is deleted or the Developer's access ends, the Developer at once stops commanding the Chargers concerned and deletes personal data obtained through the API without undue delay and other API Data within 30 days.
2.3. The Developer is an independent controller of personal data from the API.
2.4. Scheme Parties use Platform Data only to register, verify, claim and settle under an Energy Credit Scheme for the authorizing user, and to inform that user about it; GT Schedule E applies.
2.5. Meter data. The Developer uses API Data from a Meter Vendor's readings only for its own service to the user of that location. We may include in our fee for the API service any cost a Meter Vendor charges us for connecting its Meter Data Source.
2.6. Outside the EEA. A Developer established outside the EEA, in a country without an EU adequacy decision, receives personal data through the API only after signing the EU Standard Contractual Clauses with us.
2.7. Forwarding of OCPP traffic. API access gives no right to OCPP traffic of Chargers, as a copy or with control, or to place a proxy or gateway between a Charger and the Platform (GT 8.6 and 8.8).
2.8. No training of models. The Developer may not use API Data, even anonymized or aggregated, other than data it entered itself or data of Chargers it owns or leases, to train, test or improve AI or machine learning models without our prior written consent. A Developer that is a business and breaches this owes the penalty and has the duties in GT 16.7.
2.9. Source. A Developer using API Data in a registration, claim, report or publication names Plugchoice as its source where the format allows.
2.10. Proof of consent. The Developer records each user consent or instruction its access and commands rely on, and shows it to us within 5 Working Days of our request.
3. Acceptable use
3.1. GT 4.2 binds the Developer, which also may not: (a) clone the Platform, or build or improve a product or service that competes with the Platform with the SDK, Link, our documentation or code, or with API Data beyond what GT 4.2(b) and 15.5 allow; (b) benchmark or publish performance comparisons without our written consent; (c) resell, sublicense, rent or lend API access, the SDK or our code; (d) bulk-extract data beyond the connected users' own; (e) probe or test for vulnerabilities except under our Responsible Disclosure policy; (f) misrepresent its application's identity or purpose in the consent flow; (g) automate ownership transfers, access grants or other consent-type actions without the user confirming each one; (h) obtain data from our websites, documentation, apps or the Platform other than through the API within its scopes.
3.2. Rate and fair use limits in the documentation, which we may change, apply per tier, per token and across all tokens and accounts of a Developer. We may throttle or block traffic that exceeds them or burdens the Platform, without notice. Use through AI agents, scripts or other automation is the Developer's own use.
4. Commands to Chargers
4.1. The Developer answers for every command issued with its credentials or tokens.
4.2. The Developer builds proportionate safeguards and sends bulk or destructive commands only to Chargers of users who clearly enabled that.
4.3. The Developer steers a Charger only within the limits set in the Platform, never overrides a lower limit set there, and pauses its steering at our request (GT 6.10).
4.4. Server address. GT 8.7 and 8.11 apply in full. An address or setting that the Developer, its application or the SDK, or Link at its request, puts in a Charger gives the Developer no right to keep it.
4a. Data accuracy
4a.1. API Data, including a certification status such as MID, is provided as is (GT 7).
4a.2. The Developer does not present API Data as verified or certified.
4b. SDK and Link
4b.1. A "Client Secret" is a time-limited secret the Developer's server obtains from the SDK API to open Link, valid only for the user and the Chargers, sites or address in its scope.
4b.2. Link and the SDK API are available only where we enabled them, and only to open Link for the Developer's own users or Chargers. The Developer may not rebrand Link beyond our branding options or present it as its own.
4b.3. The Developer creates Client Secrets only on its own server, for a user it has signed in and with the narrowest scope the action needs, and never logs a Client Secret or passes it to anyone but the SDK or Link. It answers for everything done with its credentials and Client Secrets, including misuse by others, unless we caused it.
4b.4. The Developer may not ask for, read, store or forward login details a user enters in Link, or intercept, alter or automate the user's steps there, including the consent screen.
4b.5. Link adds Chargers to a Developer's Team only under a signed individual agreement; a fee it sets per Charger is due at setup and never refunded. The Developer is then their Account Holder and includes GT Schedule C.8 in its user terms.
4b.6. To add, set up or reconnect a Charger, Link may write our OCPP server address, its login details and network settings to that Charger and to the other Chargers Link shows that the brand's systems switch with it. Running Link is the Account Holder's instruction to do so for each Charger shown. The Developer ensures that the user running Link may give that instruction, and answers for it where that user may not.
4b.7. After a run, the Developer receives through Link only the result and, for Chargers in a user's own account, access within the scopes the user approved.
4b.8. We may change, suspend or limit the SDK, the SDK API and Link at any time.
4b.9. Clauses 4, 6.1 and 8 apply to the SDK and Link.
4b.10. SDK license. We grant the Developer a non-exclusive, non-transferable, non-sublicensable license, revocable under clauses 6.3 and 9.1, to include the SDK unmodified in its own application solely to open Link for its own users, and to distribute it only in compiled form inside that application. Beyond this license, the Developer does not publish, copy, fork, mirror, modify, wrap, port or emulate the SDK, Link or the SDK API, use them with any service other than ours, or remove our notices. Open-source components in the SDK are licensed under the licenses in its NOTICE file, which prevail for those components. The license ends with the Developer's access; the Developer then removes the SDK from new releases within 14 days. Clause 2.8 applies to a breach of this clause.
4c. Customers, onboarding and tiers
4c.1. Customer relationship. Whoever gets a Plugchoice account through the SDK, Link, the API or a Partner is our customer, under our terms, unless a signed individual agreement gives the Developer or Partner ownership of that customer relationship. We may approach and inform that customer ourselves, as the law allows, and show it our app, services and offers, also in Link.
4c.2. Onboarding. We decide the steps in Link and in the SDK flow and may change them, such as creating an account, signing in, consents, showing the Plugchoice app and our name and brand in the flow. Unless a signed individual agreement gives the Developer ownership of the customer relationship, we may make any step mandatory, such as downloading the Plugchoice app.
4c.3. No discouraging. The Developer does not hide, bypass, discourage or replace our steps, invitations, notices or brand, and does not advise users against using a Plugchoice account or the Plugchoice app.
4c.4. Tiers. We may move functions between tiers. A tier gives only what its written terms or a signed individual agreement give; everything not expressly given stays with us. That something is technically possible gives no right to it.
4c.5. These terms do not limit a user's rights under the EU Data Act, or rights under Regulation (EU) 2019/1150 (GT 14.2 and 18.6).
5. Payment endpoints
5.1. Billing, payment, payout, reimbursement and public charging endpoints are available only where we enabled them, under GT Schedule B and our payment provider's requirements.
5.2. The Developer handles full payment credentials only through the payment provider.
6. Availability, versioning and changes
6.1. The API, including beta endpoints, is provided as is.
6.2. We may add, change, deprecate or remove endpoints and fields at any time, with notice of a breaking change only where a signed individual agreement provides for it.
6.3. We may suspend or end API access with immediate effect for breach of these terms, overdue fees or an Urgent Reason.
7. Security and incidents
7.1. The Developer keeps tokens, keys and secrets confidential, uses them server-side where the tier requires, and rotates them at once on suspected compromise.
7.2. The Developer reports a security incident involving API credentials or API Data to security@plugchoice.com within 24 hours of discovering it.
7.3. Under API Professional and partner exchange, the Developer uses its own OAuth client per application and requests only the scopes it needs.
8. Liability and indemnity
8.1. The Developer indemnifies us against claims of its users and other third parties arising from its application, its use of the API, the SDK or Link, its commands to Chargers or its processing of API Data.
8.2. Verification and audit. Within 5 Working Days of our request, the Developer gives us what we reasonably need to verify its compliance, including the records under clause 2.10. Once a year, and at any time on suspicion of a breach, an independent auditor bound to confidentiality may audit its API use for us on 5 Working Days' notice; the Developer pays the audit if it shows a breach or fees due under clause 1.4. This clause does not apply to a Consumer's private use of a Personal Access Token.
9. Intellectual property
9.1. GT 16 applies. We may revoke the Developer's license to access the API and use the SDK and our sample code at once for a breach or an Urgent Reason, and otherwise with 30 days' notice.
9.2. [Intentionally left blank]
10. Changes
10.1. We may amend these terms under GT 14.
Previous versions: API and Developer Terms 2026-1, superseded on 30 October 2026 for new accounts and on 30 November 2026 for existing accounts