Time Corrections

List all time entry corrections

List the time entry correction requests of your company with cursor-based pagination, ordered by request time. Supports filtering by status (pending is the manager inbox, approved/rejected are resolved), employee_id (UUID v7) and a date range (from/to).

get/companies/{company}/time-corrections

Request

  • Base URL: https://api.factuarea.com/v1
  • URL: https://api.factuarea.com/v1/companies/{company}/time-corrections
  • 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

status'pending' | 'approved' | 'rejected' | 'null' nullable

Status to filter by: pending / approved / rejected.

employee_idstring uuid nullable

Employee ID (UUID v7) to filter by.

fromstring date-time nullable

Start date/time of the request range (ISO 8601).

tostring date-time nullable

End date/time of the request range (ISO 8601).

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": "01933a22-bf54-7e60-8c7d-4d5e6f7a8b01",
      "object": "time_correction",
      "status": "approved",
      "kind": "adjust_time",
      "time_entry_id": "01933a21-ae43-7d5f-9b6c-3c4d5e6f7a01",
      "employee_id": "01933a1f-8c21-7b3d-9e4f-1a2b3c4d5e01",
      "requested_by_id": "01933a1f-8c21-7b3d-9e4f-1a2b3c4d5edd",
      "resolved_by_id": "01933a1f-8c21-7b3d-9e4f-1a2b3c4d5eaa",
      "reason": "El fichaje de salida se registró con 30 minutos de retraso.",
      "proposed": {
        "occurred_at": "2026-05-04T18:00:00Z"
      },
      "resolved_at": "2026-05-05T08:12:00Z",
      "requested_at": "2026-05-04T18:45: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.