Time Corrections

Request a time entry correction

Request the correction of a time entry; it stays pending until a manager approves or rejects it. Returns 201 with a Location header.

  • time_entry_id, kind (add_missing_entry/adjust_time/remove_entry), reason and proposed are required.
  • A proposed time outside employment returns 422 business_rule_violation, subcode clocking_outside_employment_period.
post/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).

Headers

Idempotency-Keystring
Example:01928f10-7c0e-7c4a-9b7d-2f8a6e3c1d4b

Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide.

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.

Request body

time_entry_idstring uuid required

Clock entry ID (UUID v7) of the workday record to correct.

kind'add_missing_entry' | 'adjust_time' | 'remove_entry' required

Type of correction: add_missing_entry, adjust_time or remove_entry.

reasonstring required

Required reason for the correction request.

proposedobject

Proposed values for the correction (consistency validated in the domain).

Response

Time correction requested. The Location header contains the canonical URL of the new correction request.

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"
  }
}

Changes

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