Vacation Tracker Docs
REST API v2API referenceLeave types

Create a leave type

This API method creates a leave type and can enable it in locations right away. Requires `leave-types:write`. The acting user is the key owner, or the `X-On-Behalf-Of` user. It waits for the leave type to be created and returns it with `201`, or `202 Accepted` with an operation to poll. - `name` (1 to 32 characters) and `color` (`#RRGGBB`) are required. `isActive` defaults to `true`. - **Creating a leave type enables a leave policy in every location in `locationIds`**, all with the settings of `initialPolicy`. Every `initialPolicy` field has a default (a quota of 0 days, full-day leaves, approval required), so check it before you send `locationIds`. `locationIds` defaults to an empty array, which enables the leave type nowhere. - The policies are enabled in the background after the leave type is created, so they are not part of the response; read `GET /v2/locations/{id}/leave-policies` to confirm them, and change them with `PUT` or `PATCH /v2/locations/{id}/leave-policies/{leaveTypeId}`. - Unknown fields fail validation. Errors: `400 VALIDATION_ERROR` (`details.fields`), `400 INVALID_REQUEST_BODY`, `403 ON_BEHALF_OF_NOT_ALLOWED`, `403 FORBIDDEN`, `409 DUPLICATE_NAME` (another leave type already uses the name), `422 PLAN_LIMIT_REACHED`, and the `Idempotency-Key` codes.

POST
/v2/leave-types

Authorization

bearerAuth leave-types: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: leave-types:write

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

curl -X POST "https://example.com/v2/leave-types" \  -H "Content-Type: application/json" \  -d '{    "name": "Parental leave",    "color": "#8A2BE2"  }'
{
  "data": {
    "id": "leaveType-fcc1e5c5-ba93-479d-bd58-8f860ba10615",
    "name": "Vacation",
    "isActive": true,
    "color": "#1E90FF",
    "position": 0,
    "calendarStatus": "Busy"
  }
}
{
  "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": "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

List leave types

This API method returns the leave types of the company, active and inactive, in one response without pagination. Requires `leave-types:read`. Leave types are not limited by the key's data reach. Which locations use a leave type is returned by `GET /v2/locations/{id}/leave-policies`.

Get a leave type

This API method returns a single leave type. Requires `leave-types:read`. Errors: `404 RESOURCE_NOT_FOUND` (the leave type does not exist or was deleted).