Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
7pace Timetracker for monday.com’s API feature is currently in beta, and we are actively seeking feedback. Please get in touch with support to enable this feature.
Welcome to the documentation for the 7pace Reporting REST API, version 1.0. This API enables secure and efficient access to your 7pace worklog data and account custom field settings.
Obtain OpenAPI Specification from the Swagger section below.
Contact
If you require assistance, please contact our support team using the Support Portal.
Create an API token
The API requires JWT Bearer Token authentication. Use the following steps to create a new token:
Navigate to 7pace Timetracker Settings, click > API Tokens.
Click + Create token.
Name the token and set an expiration date.
Click Create.
Copy the API token and save it.
Authentication
Include your token in the Authorization header of each request.
Each worklog references users through different roles, each represented by a unique monday.com user ID:
AuthorId: User who originally created the worklog.
EditorId: User who last edited the worklog.
AssigneeId: User who this worklog belongs to.
Date Fields
StartedAt: The local datetime when the user started the work being logged. Format: DateTime (local, no timezone).
CreatedAt: The UTC datetime when the worklog entry was originally created in the system. Format: DateTimeOffset (UTC).
EditedAt: The UTC datetime when the worklog was last modified (for example, edited comment, changed duration). Format: DateTimeOffset (UTC).
Passing Arrays in Queries
When passing arrays (e.g., authorId, assigneeId, externalItemId), use comma-separated values:
GET /worklogs?authorId=1,2,3,4
No need to repeat the parameter. The server automatically splits the values based on commas.
Error handling
General Errors:
Title: INTERNAL_ERROR
Status: 500
Detail: Exception message.
Trace ID included (traceId) for debugging.
Timeout Errors:
Title: BAD_REQUEST
Status: 400
Special handling for timeouts.
GraphQL Errors:
Title: BAD_REQUEST
Status: 400
Detail: Single or multiple API error messages.
Special handling for timeouts.
Validation Errors:
Title: VALIDATION_ERROR
Status: 400
Detail: “One or more validation errors occurred. Check your input parameters.”
Examples
{
"title": "VALIDATION_ERROR",
"status": 400,
"detail": "One or more validation errors occurred. Check your input parameters.",
"errors": {
"queryValues": [
"Unsupported query value for key 'createdAt.end': 'Provided value '123' is not a valid date.'"
],
"queryParameters": [
"Unexpected query parameters: createdAt.stat"
]
},
"traceId": "00-163698a761739c0c-01"
}
{
"title": "BAD_REQUEST",
"status": 400,
"detail": "Your request takes too long, try to simplify it or try again later.",
"traceId": "00-abc123def456-xyz789-01"
}
{
"title": "INTERNAL_ERROR",
"status": 500,
"detail": "Unexpected error occurred.",
"traceId": "00-abc123def456-xyz789-01"
}
Rate limiting
The 7pace Reporting API applies dynamic rate limiting to ensure service stability. If rate limits are exceeded, requests will be throttled and a 429 Too Many Requests status will be returned. Clients are advised to implement exponential backoff or retry logic as needed.
Endpoints
Worklogs
GET /worklogs
Retrieve a paginated list of worklogs with optional filtering criteria.
Query parameters
Name
Type
Description
Name
Type
Description
before
string
Cursor for pagination. Returns results before the specified cursor.
after
string
Cursor for pagination. Returns results after the specified cursor.
Custom field settings describe available fields for your account, such as toggles and dropdowns. Worklogs (from /worklogs) only store field IDs and their values. To reconstruct the full custom field information, you need to:
Fetch the settings once.
When reading a worklog, match customFields.toggle.id or customFields.dropdown.id against the list from /settings/customFields.
This lets you display the field’s name, value, and type correctly.