Read a free day

GEThttps://<your-url>/api/v2/free-days/{free_day}

MCP id free-days.showAlso on this path: PATCH Update a free day, DELETE Delete a free day

Returns one free day.

Token scope: api:read:free_days
Without it: 403 insufficient-token-scope.
Permission: free_days::manage
Without it: 403 insufficient-permission.
Rate cost: 1 unit, read bucket.
Also: If-None-Match answers 304 when nothing changed. Never cached: private, no-store. Unknown query parameters are refused, never ignored.

Both are checked, scope first. A token never does more than its user. How access is checked

Request

Example: One free day with its holiday expanded

curl -G \
  'https://<your-url>/api/v2/free-days/1' \
  --data-urlencode 'include=holiday' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/free-days/1?include=holiday', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer <token>',
    'Accept': 'application/json',
  },
});

use Illuminate\Support\Facades\Http;

$response = Http::withToken('<token>')
    ->acceptJson()
    ->get('https://<your-url>/api/v2/free-days/1?include=holiday');

import requests
response = requests.request(
    'GET',
    'https://<your-url>/api/v2/free-days/1?include=holiday',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json'},
)

Response

The shape of the response, with sample values.

{
  "data": {
    "id": 1,
    "description": "Office closed for the annual outing",
    "date": "2026-07-03",
    "holiday_id": 1,
    "holiday": null,
    "created_at": "2026-03-04T09:15:00Z",
    "updated_at": "2026-03-04T09:15:00Z",
    "links": {
      "self": "https://<your-url>/api/v2/work-items/1"
    }
  }
}

The summary and detail views are identical on this resource: every field is small enough for a list row. holiday renders as an {"id": N} reference; ?include=holiday expands it, and that expansion additionally requires holidays::manage and a token scope covering the holidays prefix.

Path parameters

free_dayintegerRequired

The FreeDay's numeric id.

Query parameters

Unknown parameters are refused with 400, naming the parameter.

viewstring

Which field set to render.

summarydetaildefault

Request headers

X-Request-Idstringpattern

A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.

If-None-Matchstring

The ETag a read is conditional on. A match is answered 304 with no body.

Response 200

Returns a FreeDay in the detail view.

Headers

ETag: A strong validator of exactly this representation.
RateLimit: The IETF httpapi-ratelimit-headers form of your remaining allowance on the tightest bucket this request touched.
RateLimit-Policy: The ceiling and window of that bucket, as <limit>;w=<seconds>.
X-Request-Id: The server-generated ULID correlating this response with our logs.

Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning