Create time entry with the Toggl Track API
Creates a time entry for the connected user. Requires workspace, workspace_id, created_with and start. For a running timer, send duration -1; for past work, send duration in seconds or stop.
- Identifier
- toggl_create_time_entry
The request
POST https://connect.reportei.com/api/tools/toggl_create_time_entry/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"workspace": 1,
"workspace_id": 1,
"created_with": "<created_with>",
"start": "<start>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| workspace | integer | Yes | Id of the workspace: the default_workspace_id from Get me, the workspace_id of a project from List projects, or the wid of a client from List clients. Send it in workspace_id too. |
| workspace_id | integer | Yes | The same workspace id as workspace, from Get me, List projects or List clients. Toggl asks for it in the path and in the body. |
| created_with | string | Yes | Name of the application creating the entry, such as the name of your app. Toggl requires it. |
| start | string | Yes | Start of the entry, in UTC, as yyyy-MM-ddTHH:mm:ssZ. |
| duration | integer | No | Duration in seconds. A negative value, preferably -1, starts a running timer. |
| stop | string | No | End of the entry, in UTC, as yyyy-MM-ddTHH:mm:ssZ. With duration, it must match start plus duration. |
| description | string | No | What was done. |
| project_id | integer | No | Id of the project, from List projects. |
| tags | array | No | Tag names. A name that does not exist yet becomes a new tag. |
| billable | boolean | No | True when the time is billable. Paid plans only. |
Supported connections
Your customer connects their Toggl Track account once, with one of the modes below. The same connection serves every tool of the toolkit.
Username and password
Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/toggl_create_time_entry. It becomes your agent's tool definition with no conversion.
Other Toggl Track tools
- List projectsGETLists the projects of every workspace of the user, with their id, workspace_id, client_id and client name, billable flag and status. It is where the workspace ids come from. This route counts against the 30 requests per hour that Toggl gives each user for user-level routes, on any plan.
- List clientsGETLists the clients of every workspace of the user, with their id, name, notes, archived flag and the workspace id in wid. This route counts against the 30 requests per hour that Toggl gives each user for user-level routes, on any plan.
- Create clientPOSTCreates a client in a workspace. Requires name.
- Create projectPOSTCreates a project in a workspace, optionally for a client. Requires name. Billable is a paid feature.
- Update projectPUTUpdates the fields sent of a project and keeps the others. Archiving a project is active false.
- List time entriesGETLists the latest time entries of the connected user, up to 1000. For a window, send start_date and end_date together; for whole periods or other people, use Get summary report. This route counts against the 30 requests per hour that Toggl gives each user for user-level routes, on any plan.
- Get current time entryGETReturns the running time entry of the connected user, with its id, or null when no timer is running. This route counts against the 30 requests per hour that Toggl gives each user for user-level routes, on any plan.
- Update time entryPUTUpdates the fields sent of a time entry and keeps the others. Requires workspace and workspace_id. Changing start or stop changes the duration.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
