Skip to main content
POST
/
api
/
hris
/
v1
/
timesheet-entry
Create Timesheet
curl --request POST \
  --url https://api.bindbee.dev/api/hris/v1/timesheet-entry \
  --header 'Authorization: Bearer <token>' \
  --header 'x-connector-token: <x-connector-token>'
{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>",
      "input": "<unknown>",
      "ctx": {}
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.bindbee.dev/llms.txt

Use this file to discover all available pages before exploring further.

This endpoint creates a Timesheet Entry in the connected HRIS via Bindbee’s unified Time Sheet Entry model.

​
Provider-specific behavior

Different HRIS systems can have slightly different requirements and behaviors when creating timesheet entries. Use the accordions below to see details for each provider.

When the underlying HRIS is Bamboo HR, a Timesheet Entry can be created using a payload like:

{
  "employee": "019ab506-66a2-7f6e-b8da-09d3579a534e",
  "date": "2025-11-24",
  "start_time": "2025-11-24T08:00:00Z",
  "end_time": "2025-11-24T17:00:00Z"
}

When the underlying HRIS is Personio, a Timesheet Entry can be created using a payload like:

{
  "employee": "0198e59a-876f-748c-8e38-c56e6246f8aa",
  "break": 8,
  "date": "2025-08-04T08:00:00Z",
  "start_time": "2025-08-04T08:00:00Z",
  "end_time": "2025-08-04T16:00:00Z"
}

When the underlying HRIS is Xero, a Timesheet Entry can be created using a payload like:

{
  "employee": "0198e59a-876f-748c-8e38-c56e6246f8aa",
  "start_time": "2025-08-04T08:00:00Z",
  "end_time": "2025-08-04T16:00:00Z"
}

When the underlying HRIS is QuickBooks, a Timesheet Entry can be created using a payload like:

{
  "employee": "0198e59a-876f-748c-8e38-c56e6246f8aa",
  "hours_worked": 8,
  "date": "2025-08-04T08:00:00Z",
  "start_time": "2025-08-04T08:00:00Z",
  "end_time": "2025-08-04T16:00:00Z"
}

When the underlying HRIS is Workday, a Timesheet Entry can be created using a payload like:

{
  "employee": "019d29f5-07cf-7396-9ae1-34e5b71ad42c",
  "date": "2026-03-26",
  "hours_worked": 7.5,
  "start_time": "2026-03-26T10:00:00Z",
  "end_time": "2026-03-26T17:30:00Z",
  "additional_attributes": {
    "worker_time_block_id": "TEST_BB",
    "time_entry_code_reference_wid": "c20c857a8cf41001aa4db119cb360000",
    "out_reason_reference_id": "Out"
  }
}

  • out_reason_reference_id must be one of: Break, Meal, or Out.
  • For time_entry_code_reference_wid, search for All Time Entry Codes in the Workday portal and use the WID of any suitable code from the displayed list.
  • The selected Time Entry Code must have Units = Hours.
  • If the selected Time Entry Code has Entry Method = In/Out Only, out_reason_reference_id is required.
  • If the selected Time Entry Code has Entry Method = Hours Only, out_reason_reference_id must not be passed.

Contact Bindbee Support Team for additional details.

Contact Bindbee Support Team for additional details.

Contact Bindbee Support Team for additional details.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
x-idempotency-key
string

Key to guarantee idempotent write execution.

​
x-connector-token
string
required

Response

Successful Response