Time Entries (Field Time)

The Field Time REST API exposes a clean, versioned surface for reading and writing time entries. It supports fetching a single entry, searching with filter criteria, upserting (combined add or update) one or more entries, and reading supporting lookup values. All endpoints live under /api/ft/public/v1/ and are protected by OAuth bearer tokens. (ex. https://{JonasCustomerSubDomain}.jonasapp.com:8091/api/ft/public/v1/time-entries)

Authentication

Every /api/ft/public/ endpoint requires a valid bearer token. The controller validates the token's jpt (principal-type) claim and the caller's API license on every request. See Authentication to obtain a token, then send it as:

Authorization: Bearer <access_token>

Get a time entry

Retrieve a single time entry by its ID. Returns 200 OK with the time entry as a plain JSON object (not wrapped in an outer property), or 404 Not Found when the entry does not exist or is not visible to the caller.

GET /api/ft/public/v1/time-entries/4821

{
  "entryId": 4821,
  "userId": "JSMITH",
  "employee": "Jane Smith",
  "entryDate": "2026-06-05",
  "payroll": "REG",
  "payrollCompany": "01",
  "allocationType": "J",
  "field1": "J-1001",
  "field2": "100",
  "field3": "",
  "earningCode": "REG",
  "earningValue": 8.0,
  "occupation": "CARP",
  "union": "",
  "entryTypeId": 1,
  "status": 1,
  "inputMode": 1,
  "startTime": "07:00",
  "endTime": "15:00",
  "notes": "",
  "crewId": null,
  "reasonId": 0,
  "changeComments": null,
  "timeEntryCustomFields": [],
  "entryChangeHistories": []
}

The response omits SPA-internal fields (grid IDs, approver IDs, attachments, timer/clock metadata, computed hours/qty/dollars, and display-only names) that have no meaning to external integrators.

Search time entries

Search accepts its filter criteria as a JSON body — for example a user and a date range. Pagination is supplied with the page and pageSize query parameters.

POST /api/ft/public/v1/time-entries/search?page=1&pageSize=50

{
  "userId": "JSMITH",
  "startDate": "2026-06-01",
  "endDate": "2026-06-07",
  "companyCode": "01",
  "payrollCode": "REG",
  "status": [1, 2]
}

The response is a pagination envelope. entries uses the same field set as Get a time entry.

{
  "page": 1,
  "pageSize": 50,
  "totalCount": 2,
  "entries": [
    { "entryId": 4821, "userId": "JSMITH", "entryDate": "2026-06-05", "...": "..." },
    { "entryId": 4830, "userId": "JSMITH", "entryDate": "2026-06-06", "...": "..." }
  ]
}

Upsert time entries

The upsert endpoint accepts a batch of one or more entries in a single request — it handles both creating and updating. Entries without an entryId (or with entryId: 0) are created; entries with an existing entryId are updated.

The request below is an example only. Any entry may also include the optional fields (such as occupation, startTime/endTime, notes, crewId, and entryId for updates) in addition to the fields shown.

{
  "userId": "JSMITH",
  "entries": [
    {
      "userId": "JSMITH",
      "employee": "00001",
      "payrollCompany": "LC",
      "clientCompany": "LC",
      "country": "CA",
      "union": "UN01",
      "payroll": "WK.5",
      "earningCode": "H01",
      "earningValue": 8.25,
      "entryDate": "2026-08-24",
      "allocationType": "J/C",
      "field1": "*LYD1",
      "field2": "00000",
      "field3": "1A",
      "ppEnd": "2026/08/28",
      "inputMode": 1
    }
  ]
}

The request body has two batch-level fields:

Required entry fields. For a web-import create request, each entry requires the fields below. Codes must match values configured for the target Jonas customer.

Optional entry fields. These fields may be included on any entry, for both creates and updates unless noted otherwise.

Fields not listed above — status, display-only names and descriptions (employeeName, earningCodeDesc, entryTypeName, statusName, crewName, crewDescription), computed values (hours, qty, dollars, breakTotal, breakHour, timeEntriesRoundedTime), SPA-internal identifiers (gridId, parentId, approverId, clockTimerEntryId, timerColor, changeDetails), and entryChangeHistories — are server-computed or SPA-internal and are ignored when sent on upsert.

The response returns one result per submitted entry, in the same order, rather than the saved entry objects themselves:

{
  "entries": [
    {
      "entryId": 4821,
      "localId": "f163b4d2-5ccb-4e4b-9c3b-34cddd96aa3b",
      "success": true,
      "message": null,
      "entryChangeHistories": []
    }
  ]
}

Attachments and custom fields are not returned by upsert (v1 scope). Use Get a time entry to read back full entry details after an upsert. There is no plain unfiltered listing — use search to retrieve sets of entries.

Lookups

Supporting reference data used to populate pickers and validate the fields above. All lookup endpoints require the same bearer token as the time entry endpoints.

Entry statuses

Returns all time entry lifecycle status codes, for use with the search status filter.

Entry types

Returns configured entry types, for use with the entryTypeId field.

Input modes

Returns valid time entry input modes, for use with the inputMode field.

The three lookups above share the same code/name shape:

[
  { "code": 1, "name": "Approved" },
  { "code": 2, "name": "Pending" }
]

Change reasons

Returns valid change reason codes, for use with the reasonId field.

Crews

Returns crew IDs and names visible to a user within a company, for use with the crewId field.

GET /api/ft/public/v1/lookups/crews?company=01&user=JSMITH&search=framing

[
  { "crewId": 12, "name": "Framing Crew A", "companyCode": "01" }
]

Custom fields

Returns custom field definitions configured for a company.

GET /api/ft/public/v1/lookups/custom-fields?company=01

[
  {
    "fieldId": 3,
    "name": "PO Number",
    "fieldType": 1,
    "active": true,
    "allowedValues": [
      { "id": 1, "shortForm": "PO1", "description": "Purchase Order 1", "isDefault": false }
    ]
  }
]

Errors

Errors are returned as RFC 7807 problem detail documents. See REST API Overview → Error responses for the common status codes and shape.