Presence

List office/remote presence declarations

List the office/remote presence declarations of your company with cursor-based pagination. Supports filtering by employee_id (UUID v7), by exact day (date) or by date range (from/to, YYYY-MM-DD). Each record is one employee’s declared work location for one day. Read-only over the public API — declarations are made from the Factuarea app.

get/companies/{company}/presence/daily

Request

  • Base URL: https://api.factuarea.com/v1
  • URL: https://api.factuarea.com/v1/companies/{company}/presence/daily
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Path parameters

companystring uuid required

Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).

Query parameters

employee_idstring uuid nullable

Employee ID (UUID v7) to filter presence by.

datestring date nullable

Exact day (Y-m-d) to filter presence by.

fromstring date nullable

Start date (Y-m-d) to filter the presence range by.

tostring date nullable

End date (Y-m-d) to filter the presence range by.

limitinteger

Number of objects to return, between 1 and 100 (default 25).

starting_afterstring uuid

Cursor for forward pagination: pass the id of the last object on the previous page (the next_cursor of the previous response).

ending_beforestring uuid

Cursor for backward pagination: pass the id of the first object on the current page.

Headers

Factuarea-Versionstring date
Example:2026-06-01

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Response

has_moreboolean required

Whether more pages are available after this one.

next_cursorstring nullable required

Opaque cursor for the next page, or null when has_more is false. The example below shows the shape used by most listings; others return a different one, so pass the value back verbatim instead of validating it.

Example response

{
  "data": [
    {
      "id": "01933a50-26cb-75d7-9de4-be2f3a4b5c01",
      "object": "daily_presence",
      "employee_id": "01933a1f-8c21-7b3d-9e4f-1a2b3c4d5e01",
      "date": "2026-05-04",
      "location": "office",
      "declared_at": "2026-05-04T08:55:00Z"
    }
  ],
  "has_more": true,
  "next_cursor": "01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a0c"
}

Changes

No recorded changes to this operation across all 1 revision of this API.