Update Unique Pricing Config

Update an existing unique-date pricing config. The config is identified by its UUID in the path. The request must include the updated name and start time. On success, the response returns the updated config.

Request

Method: PUT
Path: /api/dynamic_pricing/unique_pricing_config/{uuid}

Path parameters

Name	Type	Description
uuid	string	UUID of the unique-date pricing config to update.

Body parameters

Mandatory:

Name	Type	Description
name	string	Updated name of the unique-date pricing config.
start	string	Updated start date and time in `Y-m-d H:i` format, in the station’s local time (e.g., `2026-01-01 06:00`). Seconds may be supplied; a start without them is stored as `:00`. See How a dynamic pricing schedule resolves.

Example request

curl --location --request PUT 'https://example.beenergised.cloud/api/dynamic_pricing/unique_pricing_config/<CONFIG_UUID>' \
--header 'x-api-token: <your_token>' \
--header 'Content-Type: application/json' \
--data '{
  "name": "New Year Special (updated)",
  "start": "2026-01-01 06:00"
}'

Response (200)

{
  "status": "success",
  "data": {
    "uuid": "<CONFIG_UUID>",
    "name": "New Year Special (updated)",
    "start_time": "2026-01-01 06:00:00"
  }
}

Error responses

404: Cost rate or unique pricing config not found.

{
  "status": "error",
  "message": "Cost rate not found"
}

400: Validation error (e.g., the cost rate does not use unique-date pricing).

{
  "status": "error",
  "message": "<validation message>"
}

500: Generic server error.

{
  "status": "error",
  "message": "Internal Server Error"
}