Planned
Create a new planned slot for a specific site. The slot will be created in planned state. The custom fields (e.g., custom_field_1, custom_field_2) depend on the custom fields defined in the zone related to the created slot.
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
Start time of the slot in ISO 8601 format
End time of the slot in ISO 8601 format
Optional note for the slot
Slot created successfully
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. "start_time: Field required"). Semantic errors (zone_not_found, company_not_found, company_requires_remote_id_or_pk, custom-field-not-in-zone-specs, end_time must be after start_time) keep their named codes and may use a per-field response shape.
Last updated
Was this helpful?