Skip to main content
DELETE
Delete charge schedule

Authorizations

Authorization
string
header
required

The Authorization header must be provided with a valid bearer token. Example: Authorization: Bearer {token}

Headers

sc-user-id
string
required

The identifier of the vehicle user on whose behalf the command is being executed. Vehicle commands require both the vehicleId (path) and sc-user-id (header) to identify the specific vehicle and the user who has granted permission to act on it. The bearer token is a machine-to-machine token and does not carry per-user context, so this header must be provided explicitly for every command request.

Prefer
string

Use wait=<seconds> to set how long the server waits for the request to finish. If it is still running when the wait ends, the response is 202 with the execution in PENDING status.

  • Minimum 0: always returns 202 immediately.
  • Maximum 150: a longer wait is reduced to 150.
  • Default 60: used when wait is missing or is not a whole number.

Path Parameters

vehicleId
string<uuid>
required

The unique identifier for the vehicle.

scheduleId
string<uuid>
required

The unique identifier for the schedule to delete.

Response

200 OK - The schedule was deleted within the wait time. The body holds the result.

Response to a charge schedule create or delete request. data.attributes.action identifies the operation ("create" or "delete"). data.attributes.scheduleId is the id of the schedule: for a create, it appears once the schedule has been created successfully; for a delete, it is the id from the request path. data.links.self contains the URL of this execution resource.

data
object
required