> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/wages-by-date-range.md). # Wages by Date Range Returns one row per timesheet entry with the **base activity wage only**. Commission and incentive amounts are not included - those come from the separate [Incentives by Date Range](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/incentives-by-date-range) feed. Wages and incentives are split because they have different row grains. One timesheet entry produces exactly one wage row, but zero or many incentive rows - combining them into a single feed would either double-count wages or force an aggregation that no two resorts' payroll policies agree on. This is a read-only reporting feed; nothing is written. {% hint style="info" %} **This is an alternative to, not a replacement for,** [**Paid Activities by Date Range**](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/paid-activities-by-date-range)**.** That combined feed remains fully supported and is in production use. Use Wages + Incentives if you want the two components separated; use Paid Activities if you want them together. Do not pull both for the same period - you will double-count. {% endhint %} ### Authentication ```http Authorization: Bearer {access_token} ``` ### Endpoint ```http GET {api-url}/api/timekeeping/wages ``` #### Query parameters | Parameter | Type | Description | | --------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `startDate` | date | **Required.** Start of the range (`YYYY-MM-DD`). | | `endDate` | date | **Required.** End of the range (`YYYY-MM-DD`). | | `updatedAfterLocalDateTime` | date-time | **Required.** Only entries updated after this time. Interpreted in **resort-local time**, not UTC - convert using the `timezone` from [Resort Details](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/global-settings/resort-details). | | `seasonId` | integer | **Required.** The season to report on. | ### Response `200` with an array of wage rows - **one row per timesheet entry**. | Field | Type | Description | | ----------------------------------------------------------------- | ------------------ | ----------------------------------------------------------------------- | | `seasonId` / `seasonName` | integer / string | Season the entry belongs to | | `payrollId` | string | The employee's payroll identifier | | `employeeIdentifier` | string | Resort employee identifier | | `employeeName` | string | Employee name | | `flaikEmployeeId` | integer | Flaik employee id | | `timesheetId` | integer | Timesheet entry id | | `timesheetStatus` | string | Status of the timesheet | | `timesheetDate` | string | Date of the entry | | `startTime` / `endTime` | string? | Entry start and end | | `paidActivityGroupId` / `paidActivityGroupName` | integer? / string | Activity group | | `paidActivityId` / `paidActivityName` | integer / string | The paid activity | | `paidActivityType` | string | Activity type | | `durationMinutes` | integer | Duration of the entry | | `wageTypeUsedForCalculation` | integer | Pay wage type: `1` Teaching, `2` Private, `3` Training, `4` NonTeaching | | `wageTypeUsedForCalculationName` | string? | The same value as a name | | `calculatedWageValue` | decimal | **The base wage for this entry.** Excludes commission and incentives. | | `businessStructureId` / `businessStructureName` | integer? / string? | Business structure | | `costCentre` | string? | Cost centre | | `exportBusinessStructureName` | string? | Business structure name for payroll export | | `externalId` | string? | External id | | `locationName` | string? | Location | | `parentPath` | string? | Business-structure parent path | | `payCodeId` / `payCodeName` / `payCodeType` / `payCodeCostCentre` | | Resolved pay code | | `jobCodeId` / `jobCodeName` / `jobCodeType` / `jobCodeCostCentre` | | Resolved job code | ### The three timekeeping feeds | Feed | Grain | Contains | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------ | | [Paid Activities by Date Range](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/paid-activities-by-date-range) | per timesheet entry | wages and commission combined - supported, in production use | | **Wages by Date Range** (this page) | per timesheet entry | base activity wage only | | [Incentives by Date Range](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/incentives-by-date-range) | per entry x incentive component | staff incentives and commissions | {% hint style="warning" %} There is **no entry-level join key** between the wage feed and the incentive feed - incentive rows are self-contained by design. Because the grains differ, do not sum the two feeds naively. {% endhint %} Need help? Contact . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/3.-flaik-connect-api/timekeeping/wages-by-date-range.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.