Plugsurfing · Schema
ChargingKey
Represents a charging key assigned to a user account.
CompanyEV ChargingRoamingEurope
Properties
| Name | Type | Description |
|---|---|---|
| keyId | string | Identifier used for this charging key (`uid` in the case of a physical charging key) |
| referenceId | string | Visual number for RFID and virtual keys, Plug and Charge identifier (PCID )for plug_and_charge keys |
| contractId | string | Identifier used in the context of roaming |
| name | string | Key name (usually set by end-users to name their keys when they have multiple ones). |
| validFrom | string | UTC timestamp when the charging key becomes valid. |
| validTo | string | UTC timestamp when the charging key expires. |
| type | string | Possible values include, but aren't limited to: 'tag', 'card', 'virtual', 'plug_and_charge'. |
| enabled | boolean | Indicates if the key can start a session or not |
| created | string | UTC timestamp when the charging key was created. |
| updated | string | UTC timestamp when the charging key was last updated. |
| whitelist | object | Defines whether the CPO may allow a session for this charging key when it cannot get a response from the EMP, or must always rely on realtime authorization from the EMP. Possible values: ALLOWED_OFFLI |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/plugsurfing/main/json-schema/plugsurfing-charging-key-schema.json",
"title": "ChargingKey",
"description": "Represents a charging key assigned to a user account.",
"x-generated": "2026-10-14",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_original/plugsurfing-reference-openapi.json#/components/schemas/ChargingKey",
"type": "object",
"required": [
"keyId",
"validFrom",
"validTo",
"type",
"enabled",
"created",
"updated"
],
"properties": {
"keyId": {
"type": "string",
"description": "Identifier used for this charging key (`uid` in the case of a physical charging key)"
},
"referenceId": {
"type": "string",
"description": "Visual number for RFID and virtual keys, Plug and Charge identifier (PCID )for plug_and_charge keys"
},
"contractId": {
"type": "string",
"description": "Identifier used in the context of roaming"
},
"name": {
"type": "string",
"description": "Key name (usually set by end-users to name their keys when they have multiple ones)."
},
"validFrom": {
"type": "string",
"format": "date-time",
"description": "UTC timestamp when the charging key becomes valid."
},
"validTo": {
"type": "string",
"format": "date-time",
"description": "UTC timestamp when the charging key expires."
},
"type": {
"type": "string",
"description": "Possible values include, but aren't limited to: 'tag', 'card', 'virtual', 'plug_and_charge'."
},
"enabled": {
"type": "boolean",
"description": "Indicates if the key can start a session or not"
},
"created": {
"type": "string",
"format": "date-time",
"description": "UTC timestamp when the charging key was created."
},
"updated": {
"type": "string",
"format": "date-time",
"description": "UTC timestamp when the charging key was last updated."
},
"whitelist": {
"$ref": "#/$defs/DriveApiChargingKeyWhitelistType",
"description": "Defines whether the CPO may allow a session for this charging key when it cannot get a response from the EMP, or must always rely on realtime authorization from the EMP. Possible values: ALLOWED_OFFLINE, NEVER."
}
},
"$defs": {
"DriveApiChargingKeyWhitelistType": {
"type": "string",
"enum": [
"ALLOWED_OFFLINE",
"NEVER"
],
"description": "Defines when authorization of a charging key by the CPO is allowed.\nALLOWED_OFFLINE: CPO should use realtime authorization. But when the CPO cannot get a response from the eMSP, the CPO shall allow the charging key to be used.\nNEVER: Only realtime authorization is allowed. CPO shall always send a realtime authorization for any use of this charging key to the MSP."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/plugsurfing-charging-key"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.