{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/hr.request-time-off/",
    "json": "https://www.anchorterminal.com/niches/hr.request-time-off/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/hr.request-time-off/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/hr.request-time-off/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 5 | 12 | 13 | 0 |\n\n## What counts as done\n\nA request created in the employee's name that enters the normal approval flow, or an approval recorded against the correct approver, in one call, with the request id and new status returned.\n\nHow agents ask for it: book me Friday off; request two weeks' holiday in August; approve Tom's leave request; decline the overlapping request\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **BambooHR (Bamboo HR LLC)**: POST /api/v1/time-off/requests creates a request in REQUESTED status that enters the approval workflow, and POST .../approvals completes the caller's own step in the chain, returning the updated request and status in one call.\n- **Factorial (Everyday Software, S.L.)**: Creates a Leave under a User Token files it as that employee, and Approves a Leave lets authorized users approve through the leave's approval flow with approvers_ids, one call each; webhooks report approve and reject.\n- **Remote (Remote Europe Holding B.V.)**: POST /v1/employee/timeoff creates a pending request as the employee, and POST /v1/timeoff/{id}/approve or /decline records the decision with a company-manager token, one call each, returning the time off with its status.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Deel (Deel, Inc.)**: POST /time_offs creates a request in REQUESTED status (validate first), and POST /time_offs/review approves or rejects a batch, with rejection irreversible. The docs don't say review checks that the caller is the request's approver.\n- **HiBob (Hi Bob Ltd.)**: POST /timeoff/employees/{id}/requests submits a request and webhooks report requested, approved and declined. The Time Off API lists no approve or decline endpoint, so approvals cannot be recorded through it.\n- **Humaans (Humaans Software UK Ltd)**: POST /api/time-away creates a request that is pending when approvals are required, with requestedBy and reviewedBy recorded. The reference does not document an approve call or how PATCH treats requestStatus, so recording an approval through the API is unconfirmed.\n- **Rippling (People Center, Inc. dba Rippling)**: Create leave request with status PENDING sends it through the approval chain in one call, and MCP writes follow product approval flows. The same endpoint accepts APPROVED to record leave already approved, and no approve endpoint for a pending request is in the reference list.\n- **Zoho People (Zoho Corporation Private Limited)**: Adding Leaves inserts a leave record and returns its pkId in one call. The API index lists timesheet approval but no leave approval endpoint, and the add-leave page doesn't say the record enters the approval flow.\n\n## What stops agents finishing\n\n- the API lets a token approve requests its user could not approve\n- write tools need an admin to enable them\n\n## Around it\n\nBefore: hr.whos-out. After: calendar.block-time, productivity.post-message.\n\n## Where this comes from\n\nWeight 13 of 100 in HR \u0026 employee operations: no first-hand account; rests on vendor docs (BambooHR MCP submit and approve, HiBob submit, Rippling request, Factorial approval) and the buyer check on approval rights; equal share of the remainder\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/hr.request-time-off.json, or the MCP tool get_use_case with id hr.request-time-off. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Request or approve time off",
        "url": ""
      }
    ],
    "description": "Request or approve time off: 3 companies fully do it, 5 with a limit, 12 carry the tag. Every listing in HR \u0026 employee operations with the reason and a source.",
    "facts": null,
    "h1": "Request or approve time off",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/hr.request-time-off/",
    "published": "",
    "section": "agents",
    "title": "Request or approve time off: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/hr.request-time-off/"
  },
  "tokens": {
    "markdown": 1100,
    "slim": 280
  },
  "version": 1
}
