Vacation Tracker Docs
REST API v2API referenceScheduled reports

Update a scheduled report

This API method changes a scheduled report. Requires `notifications:write`. The acting user is the key owner, or the `X-On-Behalf-Of` user. It waits for the change and returns the report with `200`, or `202 Accepted` with an operation to poll. Send only the fields you want to change; at least one field is required. Your changes are merged with the report's current values and the result is validated again, so everything you do not send is kept: - `receivers`, `locationIds`, `departmentIds`, `labelIds` and `leaveStatus`, when sent, **replace** the current list. - `sendHourUtc` and `sendMinuteUtc` are in UTC. - `leaveStatus` cannot include `CANCELLED` on update. A report whose stored `leaveStatus` includes `CANCELLED` must be sent a new `leaveStatus` without it, or the update fails with `400 VALIDATION_ERROR`. - The acting user must be an admin, or a location admin who manages every location of the report both before and after the change. Errors: `400 VALIDATION_ERROR` (`details.fields`), `400 INVALID_REQUEST_BODY`, `403 SCHEDULED_REPORTS_NOT_AVAILABLE`, `403 ON_BEHALF_OF_NOT_ALLOWED`, `403 FORBIDDEN` (the acting user is neither an admin nor a location admin, or the new `locationIds` is empty or includes a location they do not manage), `404 RESOURCE_NOT_FOUND` (the report does not exist or is outside the acting user's locations), and the `Idempotency-Key` codes.

PATCH
/v2/scheduled-reports/{id}

Authorization

bearerAuth notifications:write
AuthorizationBearer <token>

API key sent as Authorization: Bearer vt_live_<secret>. See the Authentication and Scopes sections at the top of this document for how keys are created, which scopes exist and how the key owner's role limits them.

In: header

Scope: notifications:write

Path Parameters

id*string

resource ID.

Header Parameters

Idempotency-Key?string

optional key (1 to 255 printable ASCII characters) that makes a write request safe to retry. Keys are retained for 24 hours per API key. Retrying with the same key and the same request within those 24 hours replays the original response (with the Idempotent-Replayed header). Reusing the key with a different request returns 422 IDEMPOTENCY_KEY_REUSED; retrying while the first request is still running returns 409 IDEMPOTENCY_REQUEST_IN_PROGRESS; an invalid key returns 400 INVALID_IDEMPOTENCY_KEY.

Length1 <= length <= 255
X-On-Behalf-Of?string

ID of the user the write is performed for. Requires the users:act-on-behalf scope, and the key owner must manage the target user; otherwise the request fails with 403 ON_BEHALF_OF_NOT_ALLOWED. Ignored on GET requests.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PATCH "https://example.com/v2/scheduled-reports/string" \  -H "Content-Type: application/json" \  -d '{    "receivers": [      "hr@chaochao.com",      "finance@chaochao.com"    ]  }'
{
  "data": {
    "id": "scheduledReport-8a47c61e-2b7f-4d5e-9c61-3f1c2b9e1d93",
    "name": "Monthly balances",
    "reportType": "leaveBalanceReport",
    "period": "LAST_MONTH",
    "locationIds": [],
    "departmentIds": [],
    "labelIds": [],
    "receivers": [
      "hr@chaochao.com"
    ],
    "timezone": "Europe/Belgrade",
    "sendDayOfMonth": 1,
    "sendHourUtc": 7,
    "sendMinuteUtc": 30,
    "creatorId": "user-63b17e97-d38b-4586-8498-bb4f5d2e2c14"
  }
}
{
  "operation": {
    "id": "pa_3f1c2b9e-8a47-4d5e-9c61-2b7f0e4a1d93",
    "status": "PENDING",
    "url": "/v2/operations/pa_3f1c2b9e-8a47-4d5e-9c61-2b7f0e4a1d93"
  }
}
{
  "error": {
    "code": "VALIDATION_ERROR",
    "name": "ValidationError",
    "description": "A query parameter, body field or header failed validation.",
    "resolution": "Fix the fields listed in details.fields and send the request again.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef",
    "details": {
      "fields": [
        {
          "path": "startDate",
          "message": "\"startDate\" is required"
        }
      ]
    }
  }
}
{
  "error": {
    "code": "UNAUTHORIZED",
    "name": "Unauthorized",
    "description": "The API key is missing, malformed or not recognized.",
    "resolution": "Send a valid API key in the Authorization header as Bearer followed by the full vt_live_ key.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}

{
  "error": {
    "code": "INSUFFICIENT_SCOPE",
    "name": "InsufficientScope",
    "description": "The API key does not have the scopes this request needs.",
    "resolution": "Add the scopes listed in details.requiredScopes to the key in the Vacation Tracker dashboard.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef",
    "details": {
      "requiredScopes": [
        "leaves:write"
      ]
    }
  }
}

{
  "error": {
    "code": "RESOURCE_NOT_FOUND",
    "name": "ResourceNotFound",
    "description": "The requested resource does not exist or is outside the data this key can access.",
    "resolution": "Check the ID of the resource named in details.resource and that the key owner can see it.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}

{
  "error": {
    "code": "CONFLICT",
    "name": "Conflict",
    "description": "The request conflicts with the current state of the resource.",
    "resolution": "Read the resource again and retry with up-to-date values.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}

{
  "error": {
    "code": "LEAVE_NEGATIVE_BALANCE",
    "name": "LeaveNegativeBalance",
    "description": "The user does not have enough balance for this leave.",
    "resolution": "Shorten the leave, use a different leave type, or ask an admin to adjust the quota.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}

{
  "error": {
    "code": "RATE_LIMITED",
    "name": "RateLimited",
    "description": "Too many requests were sent in a short time.",
    "resolution": "Wait a few seconds and retry, using the same Idempotency-Key for writes.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}
{
  "error": {
    "code": "INTERNAL_ERROR",
    "name": "InternalError",
    "description": "Something went wrong on our side.",
    "resolution": "Retry later, and if it keeps happening, contact Vacation Tracker support and quote the requestId.",
    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef"
  }
}

Need help?

developers@vacationtracker.io

Get a scheduled report

This API method returns a single scheduled report. Requires `notifications:read`. Errors: `403 SCHEDULED_REPORTS_NOT_AVAILABLE` (the company is not on the Complete plan), `403 FORBIDDEN` (the key owner is neither an admin nor a location admin), and `404 RESOURCE_NOT_FOUND` (the report does not exist, or the key owner is a location admin and the report has no locations or includes a location they do not manage).

Delete a scheduled report

This API method deletes a scheduled report. Requires `notifications:write`. No request body. The acting user is the key owner, or the `X-On-Behalf-Of` user; it must be an admin, or a location admin who manages every location of the report. It waits for the deletion and returns `204`, or `202 Accepted` with an operation to poll. Errors: `403 SCHEDULED_REPORTS_NOT_AVAILABLE`, `403 ON_BEHALF_OF_NOT_ALLOWED`, `403 FORBIDDEN` (the acting user is neither an admin nor a location admin), `404 RESOURCE_NOT_FOUND` (the report does not exist or is outside the acting user's locations), and the `Idempotency-Key` codes.