Add entries to user time frame

POST

/domains/{domain}/users/{user}/timeframes/{id}

Last modified:2026-09-28 00:11:17

OperationId:CreateTimeframeEntriesUser

Adds entries to an existing time frame: date ranges, holidays, or, for a custom time frame, any of the three. Requires Basic User for your own time frames, or Site Manager, Office Manager, Reseller, or Super User for the users you administer. An Office Manager can change any user in its domain, and a Site Manager any user in its own site. A user outside your reach returns 403 with Issue with timeframe access.

The write is published over the service bus (SBUS) and applied a moment later, so the call answers 202 by default. Send synchronous=yes to wait up to 10 seconds and get 200 with the time frame instead. Entry IDs are generated; do not send timeframe-id.

Specific dates. New ranges must use the recurrence type the time frame already uses, annual-month-day or doesNotRecur.

Holiday. New holidays must use the time frame's recurrence type and must not repeat one already there. A holiday whose date has passed answers 422 and nothing is added.

Days of week. A days of week time frame holds 1 entry; once it has one, this returns 400. Change it with PUT.

Custom. Any of the three arrays.

Every entry is checked before anything is published. An ID that does not exist, or that belongs to another owner than the path, returns 404 with Provided 'id' does not exist.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

The entries were published and are being applied.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠404Record not found

🟢200OK

🟠422Unprocessable Content

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

cURL

Specific datesHolidayCustom

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/example.com/users/1001/timeframes/7ae64ba3e46676fc728618a616e92424' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "timeframe-specific-dates-array": [
        {
            "timeframe-specific-dates-begin-date": "20261231",
            "timeframe-specific-dates-begin-time": "0000",
            "timeframe-specific-dates-end-date": "20261231",
            "timeframe-specific-dates-end-time": "2359",
            "timeframe-recurrence-type": "annual-month-day",
            "timeframe-recurrence-custom-interval": "",
            "timeframe-recurrence-custom-interval-count": "",
            "timeframe-recurrence-custom-interval-option": "",
            "timeframe-recurrence-end-option": "",
            "timeframe-recurrence-end-date": ""
        }
    ]
}'

Response Example

202 - Specific dates

The entries were published and are being applied. Send synchronous=yes to get the time frame back instead.

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-09-28 00:11:17

List domain time frame names

Delete user time frame