---
title: "Retrieve the time tracking settings"
method: GET
path: "/companies/{company}/time-tracking-settings"
tags: ["Time Tracking Settings"]
---

# Retrieve the time tracking settings

`GET /companies/{company}/time-tracking-settings`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/time-tracking-settings`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Return the time tracking configuration of your company: the overtime computation basis (`weekly`/`daily`) and thresholds, the rounding tolerance and the forgotten-clock-in reminder settings. If your company has not configured it yet, the defaults are returned with `id: null` — the first update materialises the row.

## Path parameters

- `company` string, uuid, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` TimeTrackingSettings, required: The per-company time tracking configuration for the Control Horario module: the overtime computation basis and thresholds, the rounding tolerance and the forgotten-clock-in reminder settings. The public `id` is the UUID v7 of the settings row, or `null` until the first PUT materialises it.
    - `id` string, uuid, nullable, required: UUID v7 of the settings row, or `null` while the company has not materialised it yet (the first PUT creates the row).
    - `object` 'time_tracking_settings', required: Always `time_tracking_settings`.
    - `overtime_basis` 'weekly' | 'daily', required: Overtime computation basis: `weekly` aggregates the week, `daily` computes per day.
    - `overtime_daily_threshold_minutes` integer, nullable, required: Daily overtime threshold in minutes, or `null` to derive it from the schedule.
    - `overtime_weekly_threshold_minutes` integer, nullable, required: Weekly overtime threshold in minutes, or `null` to derive it from the schedule.
    - `overtime_tolerance_minutes` integer, required: Rounding tolerance for overtime in minutes.
    - `clock_in_reminder_enabled` boolean, required: Whether the forgotten clock-in reminder is enabled.
    - `clock_in_reminder_grace_minutes` integer, required: Grace minutes after the planned start time before reminding.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company. `profile_not_found`: the company in the path does not exist, is not in the API key scope or belongs to the other environment (live or test).
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)