Update References
Updates slot references and custom fields. The custom fields (e.g., custom_field_1, custom_field_2) depend on the custom fields defined in the zone related to the updated slot. This endpoint allows partial updates to slot references and custom fields without affecting other slot properties.
Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.
Example of authenticated request
$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
The slug identifier of the site
List of reference strings for the slot
Value for the first custom field (if defined in the zone)
Value for the second custom field (if defined in the zone)
Slot references updated successfully
Unique identifier for the slot
Start time of the slot in ISO 8601 format
End time of the slot in ISO 8601 format
Current state of the slot
Optional note for the slot
Bad request - invalid input. Structural validation errors are returned as a single non_field_errors umbrella with code: ["invalid_input"] and one detail entry per offending field, formatted as "<dotted-loc>: <message>" (e.g. "references: Field required" or "references[0]: String should have at most 128 characters"). Custom-field-vs-zone-specs errors keep a per-field response shape.
Last updated
Was this helpful?