Workspaces

Filter by color ID. Provide a comma-separated list of color IDs.

Filter for only archived projects, or include or exclude archived projects from the results. Options are only, exclude, and include.

Return only budgeted projects (true) or only non-budgeted projects (false).

Filter by a custom field choice value, represented as a string with the custom field ID, followed by a colon, and then comma-separated custom field choice value IDs. The custom field choice value can also be the word blank. Multiple custom fields can be delimited by semicolons or by parentheses and colons.

The following formats are supported:

• custom_field_ID:choice_value_ID
• custom_field_ID:choice_value_1_ID,choice_value_2_ID
• custom_field_ID:blank
• (custom_field_1_ID:choice_value_1_ID,choice_value_2_ID):(custom_field_2_ID:choice_value_3_ID).

Filter by a custom field currency value, represented as a string with the custom field ID, followed by a colon, and then the currency value. Optionally, the currency ISO code can be supplied as well, separated from the currency value by another colon. Multiple custom fields can be delimited by semicolons or by parentheses and colons. The following formats are supported:

• (1:200.2:USD):(2:100).

Filter by a custom field date value, represented as a string with the custom field ID, followed by a colon, the starting date, another colon, and then the ending date. You can provide both a starting date and ending date, or provide just one. Multiple custom fields can be delimited by semicolons or by parentheses and colons. The following formats are supported:

• (1:2014-12-05:2014-12-25):(2:2014-12-05).

Filter by a custom field number value, represented as a string with the custom field ID, followed by a colon, and then the number value. Multiple custom fields can be delimited by semicolons or by parentheses and colons. The following formats are supported:

• (1:200):(2:101).

Filter by a custom field text value, represented as a string with the custom field ID, followed by a colon, and then the text value. Multiple custom fields can be delimited by semicolons or by parentheses and colons. The following formats are supported:

• (1:something):(2:else).

Return only projects where the authenticated user can create expenses or time entries (true) or only projects where the user can't (false).

Filter for records created after a specified datetime. The datetime must be in ISO 8601 format.

(Deprecated) Use the created_before and created_after filters instead.

Filter for projects created between a specified date range. Format as from_date;to_date. Dates must be in ISO 8601 format. For example, 2014-12-05;2014-12-25.

Filter for records created before a specified datetime. The datetime must be in ISO 8601 format.

Filter for projects created by a specific user(s). Provide a comma-separated list of user IDs. For example, 10,20.

Filter for projects where the authenticated user is on the provider team. When included in your request, this filter is always processed as true; the actual value you provide is ignored.

Filter for projects with date custom field value(s) within a specified range. Format as custom_field_id:from_date:to_date;custom_field_id:from_date:to_date. Multiple custom fields can be delimited by semicolons. Dates must be in ISO 8601 format. For example, 1:2014-12-05:2014-12-25;2:2015-12-05:2015-12-25.

Filter for projects with number custom field value(s) within a specified range. Format as custom_field_id:min:max;custom_field_id:min:max. Multiple custom fields can be delimited by semicolons. For example, 42:20:10;43:50:100.

Filter for projects that are due after the specified date. Can be used with due_date_before to filter by a date range. The date must be in ISO 8601 format.

Filter for projects that are due before the specified date. Can be used with due_date_after to filter by a date range. The date must be in ISO 8601 format.

Filter out specific projects from the results. Provide a comma-separated list of workspace IDs.

Filter the objects based on the external message of their associated external references. This is an exact match.

Filter by the status of the external object in the external system.

Filter by the type of the external object this external reference belongs to.

Filter by the id of the external object this external reference belongs to.

Filter for objects that correlate to the specified external object IDs. Provide a comma-separated list of up to 200 external IDs.

Filter by the name of the provider for integration.

Filter by the status of the integration, this can be successful or fail.

Return only projects that the authenticated user can view, has financial access in, and is on the provider team. If false, no filtering is applied.

Filter for projects where the user with the specified user ID can approve time.

Return only projects that have an approver (true) or only projects that don't (false).

Filter by whether or not the object has external references.

Filter for projects where the user with the specified user ID is on the provider team.

Filter for projects where the user with the specified user ID is a participant.

Filter for projects where the authenticated user is a participant.

Filter by the presence of a custom field value for the specified comma-separated custom field ID(s).

Any of the below associations can be included in your request by providing the include param, e.g. include=association1,association2.

• account_color (AccountColor) - Retrieves the color of the workspace. The response will include account_color_id, which references the data in the account_colors top-level key.
• account_insights_mappings (AccountInsightsMapping) - Retrieves the Insights dynamic dashboards in the workspace. The response will include account_insights_mapping_ids, which references the data in the account_insights_mappings top-level key.
• approver (User) - Retrieves the first approver (as determined by user ID) on the workspace who is viewable to the current user. The response will include approver_id, which references the data in the users top-level key.
• approvers (User) - Retrieves all time approvers on the workspace who are viewable to the current user. The response will include approver_ids, which references the data in the users top-level key.
• creator (User) - Retrieves the user who created the project. The response will include creator_id, which references the data in the users top-level key. If the creator has left the project, you can use primary_counterpart to get the provider-side team lead.
• current_status_report (StatusReport) - Retrieves the most recent project status report from today. The response will include current_status_report_id, which references the data in the status_reports top-level key.
• current_user_participation (Participation) - Retrieves the workspace participation of the current user. The response will include current_user_participation_ids, which references the data in the participations top-level key.
• custom_field_values (CustomFieldValue) - Retrieves custom field values for the workspace. The response will include custom_field_value_ids, which references the data in the custom_field_values top-level key.
• external_references (ExternalReference) - Includes references to external integrations for this object.
• financial_viewers (User) - Retrieves the users on the project who have financial access. The response will include financial_viewer_ids, which references the data in the users top-level key.
• next_uncompleted_milestone (Story) - Retrieves the next project milestone that is not complete. The response will include next_uncompleted_milestone_id, which references the data in the stories top-level key.
• participants (User) - Retrieves users that are participating in the project. The response will include participant_ids, which references the data in the users top-level key.
• participations (Participation) - Retrieves the participations of each participant in the project. The response will include participation_ids, which references the data in the participations top-level key.
• possible_approvers (User) - Retrieves the users that can be made time approvers on the workspace. The response will include possible_approver_ids, which references the data in the users top-level key.
• primary_counterpart (User) - Retrieves the lead of the Clients team. The response will include primary_counterpart_id, which references the data in the users top-level key.
• primary_maven (User) - Retrieves the lead of the Providers team. The response will include primary_maven_id, which references the data in the users top-level key.
• primary_workspace_group (WorkspaceGroup) - Retrieves the primary group associated with the project. The response will include primary_workspace_group_id, which references the data in the workspace_groups top-level key.
• status_reports (StatusReport) - Retrieves the status reports for the workspace. The response will include status_report_ids, which references the data in the status_reports top-level key.
• timesheet_submissions (TimesheetSubmission) - Retrieves the list of all submitted timesheets which the user can approve on the project. The response will include timesheet_submission_ids, which references the data in the timesheet_submissions top-level key.
• workspace_groups (WorkspaceGroup) - Retrieves groups associated with the project that is visible to the current user. The response will include workspace_group_ids, which references the data in the workspace_groups top-level key.
• workspace_resources (WorkspaceResource) - Retrieves the named resources for the workspace. The response will include workspace_resource_ids, which references the data in the workspace_resources top-level key.
• workspace_resources_with_unnamed (WorkspaceResource) - Retrieves the named and unnamed resources for the workspace. The response will include workspace_resources_with_unnamed_ids, which references the data in the workspace_resources top-level key.

Include (true) or exclude (false) archived projects from the results.

Filter for projects with a title that match the specified string. This filter is not case sensitive. This filter functions as a "starts with" filter for each word in project titles.

Additionally, the following common words (known as stop words) are ignored: a, an, and, are, as, at, be, but, by, for, if, in, into, is, it, no, not, of, on, or, such, that, the, their, then, there, these, they, this, to, was, with.

Filter for projects which have a milestone percent completion within the specified range. Provide two comma-separated numbers. For example, 15,30.

Filter for projects that are on the authenticated user’s account and within the organization hierarchy the authenticated user is a part of. Requires the Report Viewer account permission or above.

Filter for projects that are on the same account as the authenticated user.

Allows you to request one or more resources directly by ID. Multiple IDs can be supplied in a comma separated list, like GET /api/v1/workspaces.json?only=5,6,7.

Filter for projects which the authenticated user can join and are within the organization hierarchy the user is a part of.

Filter for projects which the authenticated user is participating in or can join.

Filter for projects that are on the same account as the authenticated user, where the user is on the provider team, and where they have financial access or higher.

Allows you to request one or more optional fields as an array.

Supply order with the name of a valid sort field for the endpoint and a direction.

Valid values: amount_paid:asc, amount_paid:desc, color_name:asc, color_name:desc, created_at:asc, created_at:desc, custom_field:<custom_field_id>:asc, custom_field:<custom_field_id>:desc, due_date:asc, due_date:desc, last_viewed:asc, last_viewed:desc, percentage_complete:asc, percentage_complete:desc, price:asc, price:desc, provider_lead_name:asc, provider_lead_name:desc, search, start_date:asc, start_date:desc, status:asc, status:desc, title:asc, title:desc, updated_at:asc, and updated_at:desc.

Note: The custom_field:<custom_field_id>:asc and custom_field:<custom_field_id>:desc options do not support multi-choice custom fields.

Filter for projects that are on the same account as the authenticated user, that the user is participating in, and that are within the organization hierarchy the user is a part of.

Filter for projects that have pending timesheet submissions within a specified date range. Format as from_date;to_date. Dates must be in ISO 8601 format. For example, 2014-12-05;2014-12-25.

Filter for projects with the specified provider team leads. Provide a comma-separated list of user IDs. For example, 10,20.

Return only projects that require time approvals (true) or only projects that don't (false).

Return only projects that require expense approvals (true) or only projects that don't (false).

Filter for projects that have a specific choice selected for a choice custom field. Format as custom_field_id:choice_ids;custom_field_id:choice_ids. Pass none to indicate no selection. Multiple custom fields can be delimited by semicolons. For example: 1:3,2;4:2,none.

Return only projects in the estimate stage or project stage. Options are estimate and project.

Filter for projects that start after the specified date. Can be used with start_date_before to filter by a date range. The date must be in ISO 8601 format.

Filter for projects that start before the specified date. Can be used with start_date_after to filter by a date range. The date must be in ISO 8601 format.

Filter for records updated after a specified datetime. The datetime must be in ISO 8601 format.

Filter for records updated before a specified datetime. The datetime must be in ISO 8601 format.

Filter for projects where the user with the specified ID is not participating.

Return only projects where the authenticated user can approve time. Can be used in combination with the include_archived filter.

Exclude by the existence of an external reference with the specified service name.

Any of the below associations can be included in your request by providing the include param, e.g. include=association1,association2.

• account_color (AccountColor) - Retrieves the color of the workspace. The response will include account_color_id, which references the data in the account_colors top-level key.
• account_insights_mappings (AccountInsightsMapping) - Retrieves the Insights dynamic dashboards in the workspace. The response will include account_insights_mapping_ids, which references the data in the account_insights_mappings top-level key.
• approver (User) - Retrieves the first approver (as determined by user ID) on the workspace who is viewable to the current user. The response will include approver_id, which references the data in the users top-level key.
• approvers (User) - Retrieves all time approvers on the workspace who are viewable to the current user. The response will include approver_ids, which references the data in the users top-level key.
• creator (User) - Retrieves the user who created the project. The response will include creator_id, which references the data in the users top-level key. If the creator has left the project, you can use primary_counterpart to get the provider-side team lead.
• current_status_report (StatusReport) - Retrieves the most recent project status report from today. The response will include current_status_report_id, which references the data in the status_reports top-level key.
• current_user_participation (Participation) - Retrieves the workspace participation of the current user. The response will include current_user_participation_ids, which references the data in the participations top-level key.
• custom_field_values (CustomFieldValue) - Retrieves custom field values for the workspace. The response will include custom_field_value_ids, which references the data in the custom_field_values top-level key.
• external_references (ExternalReference) - Includes references to external integrations for this object.
• financial_viewers (User) - Retrieves the users on the project who have financial access. The response will include financial_viewer_ids, which references the data in the users top-level key.
• next_uncompleted_milestone (Story) - Retrieves the next project milestone that is not complete. The response will include next_uncompleted_milestone_id, which references the data in the stories top-level key.
• participants (User) - Retrieves users that are participating in the project. The response will include participant_ids, which references the data in the users top-level key.
• participations (Participation) - Retrieves the participations of each participant in the project. The response will include participation_ids, which references the data in the participations top-level key.
• possible_approvers (User) - Retrieves the users that can be made time approvers on the workspace. The response will include possible_approver_ids, which references the data in the users top-level key.
• primary_counterpart (User) - Retrieves the lead of the Clients team. The response will include primary_counterpart_id, which references the data in the users top-level key.
• primary_maven (User) - Retrieves the lead of the Providers team. The response will include primary_maven_id, which references the data in the users top-level key.
• primary_workspace_group (WorkspaceGroup) - Retrieves the primary group associated with the project. The response will include primary_workspace_group_id, which references the data in the workspace_groups top-level key.
• status_reports (StatusReport) - Retrieves the status reports for the workspace. The response will include status_report_ids, which references the data in the status_reports top-level key.
• timesheet_submissions (TimesheetSubmission) - Retrieves the list of all submitted timesheets which the user can approve on the project. The response will include timesheet_submission_ids, which references the data in the timesheet_submissions top-level key.
• workspace_groups (WorkspaceGroup) - Retrieves groups associated with the project that is visible to the current user. The response will include workspace_group_ids, which references the data in the workspace_groups top-level key.
• workspace_resources (WorkspaceResource) - Retrieves the named resources for the workspace. The response will include workspace_resource_ids, which references the data in the workspace_resources top-level key.
• workspace_resources_with_unnamed (WorkspaceResource) - Retrieves the named and unnamed resources for the workspace. The response will include workspace_resources_with_unnamed_ids, which references the data in the workspace_resources top-level key.