Plugsurfing
Plugsurfing provides a seamless EV charging experience across Europe, offering drivers access to a large network of charging stations through its mobile app and white‑label solutions for businesses. The platform supports roaming via the OCPI 2.2.1 protocol, enabling operators to connect to the Plugsurfing network with real‑time charger data, tariffs, and availability. It also offers APIs for developers to embed charging functionality into apps, in‑car navigation, and other digital services, fostering a more integrated electric mobility ecosystem.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Plugsurfing the way a machine reads it — 27 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Plugsurfing scores 47.8/100 (developing), with a separate agent-readiness read of 47/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company publishes no developer documentation host and no machine-readable contract on its own domain
This is an honest zero, not a gap in our research. Plugsurfing does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://developer.plugsurfing.com/mcp→ HTTPhttps://partnersupport.plugsurfing.com/mcp→ HTTP 401https://www.plugsurfing.com→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Plugsurfing's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/plugsurfing/"
title="Plugsurfing on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/plugsurfing.svg"
alt="Plugsurfing Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/plugsurfing/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/plugsurfing/"
title="Plugsurfing on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/plugsurfing/card.svg"
alt="Plugsurfing Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Plugsurfing
Each block below is one kind of artifact we hold for Plugsurfing. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Drive API
The Drive API provides comprehensive access to Plugsurfing's charging infrastructure network.
Plugsurfing Charging Key Orders API
Handle the ordering and fulfillment process for physical charging keys
Plugsurfing Charging Keys API
Manage physical and virtual charging keys including creation, activation, updates, and status management. Essential for user access to charging stations.
Plugsurfing Drive API
The Drive API API from Plugsurfing — 0 operation(s) for drive api.
Plugsurfing EMP Charging Keys API
E-Mobility Provider specific endpoints for managing charging keys
Plugsurfing EMP Fleets API
E-Mobility Provider specific endpoints for managing fleets
Plugsurfing EMP Geosearch API
E-Mobility Provider specific endpoints for location search and information
Plugsurfing EMP Orders API
E-Mobility Provider specific endpoints for managing orders
Plugsurfing EMP Sessions API
E-Mobility Provider specific endpoints for managing charging sessions
Plugsurfing Geosearch API
Search and retrieve detailed information about charging locations and stations
Plugsurfing Payment Options API
Manage payment methods and handle transaction processing for charging services
Plugsurfing Remote Charging API
Control charging sessions remotely including starting and stopping sessions, and monitoring session status
Plugsurfing Sessions API
Access and manage charging session data including history, status, and detailed session information
Plugsurfing User Groups API
Manage user group memberships
Plugsurfing Users API
Manage user accounts including creation, retrieval, updates, and deletion. Handles user-specific data and preferences.
Plugsurfing Vouchers API
Redeem vouchers
Scroll within the panel for all 16 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Plugsurfing Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Plugsurfing Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Plugsurfing API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ChargingKey
JSON SCHEMAEmpChargingKeyOrdersProduct
JSON SCHEMAEmpChargingKeyPostRequest
JSON SCHEMALocation
JSON SCHEMAPrepaidBalance
JSON SCHEMASession
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Plugsurfing — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/plugsurfing · machine-readable index on apis.io
This is an independent, third-party profile of Plugsurfing, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.