Add a timesheet

post

https://api.timeero.app/api/public/timesheets

Add a new timesheet for specific user with in a company.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

A list of valid timezones to be used in API requests can be found here: Timezones . Please note that when using ISO 8601 date/time values with an offset, the offset must match the provided timezone. If no timezone is provided, it will default to the company's timezone.

Body Params

user_id

integer

required

The ID of the timesheet owner

start

date-time

required

The date and time when the user clocked in, in ISO 8601 format, e.g: YYYY-MM-DDTHH:MM:SS±HH:MM.

end

date-time

The date and time when the user clocked out, in ISO 8601 format: YYYY-MM-DDTHH:MM:SS±HH:MM. Set to null if the user is still clocked in.

job_id

integer

The ID of the job associated with the timesheet entry.

task_id

integer

The ID of the task associated with the timesheet entry.

mileage

float

The distance(in miles) traveled during the timesheet period.

clock_in_timezone

string

The timezone in which the clock-in time was recorded. The company's timezone will be used if none is provided. And it must match the offset when ISO 8601 offset is set.

clock_out_timezone

string

The timezone in which the clock-out time was recorded. Set to null if the user has not clocked out yet. The company's timezone will be used if none is provided. And it must match the ISO 8601 offset when set.

notes

string

Additional notes or comments for the timesheet entry.

custom_fields

json

enum

An object containing user-defined timesheet's custom fields. Each key is a custom field ID, and each value is the corresponding field value. Field IDs and values vary depending on the configuration. Only available on Permium plan. For more details, see the Custom Field Guide.

Allowed:

Responses

200

422Unprocessable Entity

500Internal Server Error