Skip to main content
Version: v20251216

​
Availability

The API’s target availability is defined in two categories:
  • Core features (99.7%)
  • Secondary features (99%)
These targets exclude scheduled maintenance or planned downtime. Availability is calculated as the percentage of uptime for the features listed above on a monthly basis. Downtime is measured in minutes when a feature is inaccessible.
A major outage occurs when 100% of users are affected.
A partial outage, where only a subset of users is impacted, counts as 30% of its timespan toward the total downtime in a month.

​
Core Features

  • User registration
  • RFID charging (availability excludes downtime caused by user error, such as incorrect handling of the charger)
  • Geosearch
The target availability for core features is 99.7% (<2.1 hours of downtime per month).

​
Secondary Features

  • Key ordering
  • Subscription join
  • Remote charging (availability excludes downtime caused by user error, such as incorrect handling of the charger)
  • Other new features
The target availability for secondary features is 99% (<7.2 hours of downtime per month).

​
API Response Time

​
Definition

The API Response Time is the time measured in milliseconds from the moment the last byte of a request is received, to the moment the first byte of the response is sent from the API. p98 response time refers to the maximum response time for the fastest 98% of responses (excluding the slowest 2%).

​
Response Time Targets

Target p98 response times for the Drive API:
  • Geosearch: 900ms (for a radius <10km, or aggregated for larger radii)
  • Charging Key Activation: 900ms
  • User Registration: 1400ms

​
Asynchronous Processes

  • Charging Key creation: up to 10 seconds
  • Charging Key propagation to CPOs: up to 48 hours

​
Response Time Dependencies

Response times may vary across API endpoints due to dependencies on external systems, such as:
  1. Start/Stop Session: These requests rely on external CPO systems to initiate/end the session and a Payment Service Provider like Stripe for payment processing afterward.
  2. Charging Key: Requests for charging key ordering, activation, updates, and plug-and-charge functionality depend on external CPOs for distributing the new key information.

​
Maintenance

We recognize the importance of transparent communication regarding incremental changes and necessary maintenance to ensure platform health. We follow a notification schedule based on the type of upgrade needed in the system. Please refer to your contract with Plugsurfing for details on the notification schedule. Plugsurfing will communicate scheduled maintenance via the Status Page. Please subscribe for the latest updates.