Read an absence

GEThttps://<your-url>/api/v2/absences/{absence}

MCP id absences.showAlso on this path: PATCH Update an absence, DELETE Delete an absence

Returns one absence.

Token scope: api:read:absences
Without it: 403 insufficient-token-scope.
Permission: absences::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 absence with both users expanded

curl -G \
  'https://<your-url>/api/v2/absences/1' \
  --data-urlencode 'include=user,manager' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/absences/1?include=user%2Cmanager', {
  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/absences/1?include=user%2Cmanager');

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

Response

The shape of the response, with sample values.

{
  "data": {
    "id": 1,
    "user_id": 1,
    "user": {
      "id": 1
    },
    "manager_id": 1,
    "manager": null,
    "start": "2026-03-02T08:00:00Z",
    "end": "2026-03-06T17:00:00Z",
    "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. user and manager render as {"id": N} references; ?include=user,manager expands them, and that expansion additionally requires users::read and a token scope covering the users prefix. An absence whose employee has since been deleted keeps the reference form rather than expanding.

Path parameters

absenceintegerRequired

The Absence'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 Absence 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