Skip to main content
POST
Sensors / Create

Authorizations

Authorization
string
header
required

OAuth2 Bearer Authorization

Scopes

asset:sensors

Headers

Accept-Language
string

BCP 47 language tag for content negotiation (e.g. en, de-DE).

Example:

"en"

Body

application/json

Creates a parking sensor and links it to a chargepoint of the authenticated client. Required permission: asset:sensors:create. Available contexts: API Key, User.

chargepoint_uuid
string
required

The UUID of the charge point this sensor is assigned to. Each chargepoint can have at most one parking sensor.

Pattern: ^[a-f0-9]{8}\-[a-f0-9]{4}\-4[a-f0-9]{3}\-[89ab][a-f0-9]{3}\-[a-f0-9]{12}$
last_status
enum<string>

Most recent occupancy status reported by the sensor. Allowed values: Available (spot free), Occupied (vehicle charging), Parked (vehicle blocks the spot without charging), Unavailable (sensor or spot out of service), Unknown (no valid status yet).

Available options:
Available,
Occupied,
Parked,
Unavailable,
Unknown
Example:

"Occupied"

name
string

Human-readable label of the sensor.

Maximum string length: 255
Example:

"Sensor Bay 3"

interface_name
string

Name of the external interface delivering sensor data, identifying which partner system or sensor provider is the source of the status updates.

Maximum string length: 255
ext_id
string

Identifier of the sensor in the upstream system or hardware vendor.

Maximum string length: 255

Response

Created sensor.

sensor
object
required

The parking sensor record with its charge point assignment and last reported status.