Kantata Kantata OX Knowledge Base
Release Notes
Status Page

Workspaces

Workspaces (also called projects) represent the space in which Kantata OX users plan, communicate, and collaborate.

Fetching a list of Workspaces

Gets a list of projects.

By default, archived projects are not returned in the response. Use the include_archived=true filter to retrieve archived projects.

This endpoint returns structured Workspace objects. As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array and will be indexed by ID in the workspaces top-level JSON key. Please see our Response Format section for more information.

Request
query Parameters
account_color_ids
string

A comma separated string of color ids to filter on.

archived
string

Only includes archived project, based on the specified option. Options are 'only', 'exclude', or 'include'.

budgeted
boolean

Only includes projects that are budgeted. True for only budgeted budgeted; false for only non-budgeted.

by_custom_choice_value
string

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).
by_custom_currency_value
string

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).
by_custom_date_value
string

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).
by_custom_number_value
string

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).
by_custom_text_value
string

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).
can_create_line_items
boolean

Only includes projects where the current user can create expenses or time entries.

created_after
string <date-time>

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

created_at
string

(Deprecated) Use created_before and created_after filters instead. Only includes projects created between the specified date range. For example, '2014-12-05;2014-12-25'.

created_before
string <date-time>

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

creator
string

Only includes projects in which the specified set IDs belong to the creator of the project. For example, '10,20'.

current_user_is_maven_participant
boolean

Only includes projects in which the requester is a Provider in the project.

custom_date_range
string

Only includes projects with custom field date values within the specified range. Argument is formatted as field_id:from:to;.

custom_integer_ranges
string

Only includes projects containing integer custom fields with values within the specified range (specified by field_id:min:max, delimited by semi-colons). For example '42:20:10;.

due_date_after
string <date>

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.

due_date_before
string <date>

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.

except
string

Only includes projects that do not match the specified IDs.

external_reference_external_message
string

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

external_reference_external_status
string

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

external_reference_service_model
string

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

external_reference_service_model_ref
integer <int32>

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

external_reference_service_model_refs
string

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

external_reference_service_name
string

Filter by the name of the provider for integration.

external_reference_status
string

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

financials_viewable_by_user
boolean

Only includes projects that can be viewed by the requester (where the requester has financial access and is a provider on the project).

for_approver
integer <int32>

Only includes projects in which the user corresponding to the passed ID can approve time.

has_approvers
boolean

Only includes projects that have an approver.

has_external_references
boolean

Filter by whether or not the object has external references.

has_maven_participant
integer <int32>

Only includes projects which the specified user is participating as a Provider.

has_participant
integer <int32>

Only includes projects in which the specified user is an active participant.

has_participation
boolean

Only includes projects in which the user that is logged-in is a participant.

has_value_for_custom_field_ids
string

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

include
string

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.
  • 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_archived
boolean
Default: false

Only includes archived projects (if set as 'true').

matching
string

Only includes projects in which the title matches the search string.

milestone_weight_percentage_complete
string

Only includes projects with milestones in which the percentage complete is within the specified range. For example, 15,30.

on_account_by_orgs
boolean

Filters for projects on the user's account. Filters for projects that respect the heirarchy of organizations. Only available to report viewers.

on_my_account
boolean

Only includes projects belonging to the account of the user that is logged-in.

only
string

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.

only_joinable
boolean

Filters for projects which can be joined by the user. Filters for projects that respect the heirarchy of organizations.

only_participating_or_joinable
boolean

Filters for projects that can be joined or participated in by the user.

only_project_manager_in
boolean

Filters for projects on the user's account. Filters for projects in which the user is participating as a consultant. Filters where their access if financial or greater.

optional_fields
Array of strings

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

Items Enum: "client_lead_name" "provider_lead_name" "stage" "estimated_minutes" "total_invoiced" "total_minutes_approved" "billable_minutes" "non_billable_minutes" "minutes_logged" "incoming_email_address" "lock_date"
order
string
Default: "updated_at:desc"

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.

page
integer <int32>
Default: 1
participant_or_org_member_in
boolean

Filters for projects on the user's account. Filters for projects in which the user is participating. Filters for projects that respect the heirarchy of organizations.

pending_timesheet_submissions
string

Only includes projects that have pending timesheet submissions within the specified date range. For example, '2014-12-05;2014-12-25'.

per_page
integer <int32> <= 200
Default: 20
provider_lead
string

Only includes projects in which the specified set IDs belong to Provider Leads in the project. For example, '10,20'.

require_time_approvals
boolean

Only includes projects that require time approvals.

requiring_expense_approval
boolean

Only includes projects that require expense approvals.

search
string
selected_choices
string

Only includes projects with the selected custom field choice value. Argument is formatted as field_id:choice_ids;. 'none' represents no selection. For example: 1:3,2;4:2,none.

start_date_after
string <date>

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.

start_date_before
string <date>

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.

updated_after
string <date-time>

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

updated_before
string <date-time>

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

user_not_participating
integer <int32>

Only includes projects in which the specified user is not participating.

viewable_for_time_administration
boolean

Only includes projects where the current user can approve time. Takes include_archived option.

without_external_reference_service_name
string

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

workspace_groups
string

Only includes projects that are associated with the specified project groups. For example, '10,20'.

Responses
200

A list of Workspaces have been retrieved.

Response Schema: application/json
count
integer <int32>
object
Array of objects
object
object
object
object
object
object
object
object
object
object
object
400

Bad Request

401

Unauthorized request

403

Forbidden request

404

Page Not Found

422

Unprocessable Entity

503

Service is unavailable

get/workspaces
Request samples
Response samples
application/json
{
  • "count": 0,
  • "meta": {
    },
  • "results": [
    ],
  • "workspaces": {
    },
  • "external_references": {
    },
  • "stories": {
    },
  • "users": {
    },
  • "participations": {
    },
  • "timesheet_submissions": {
    },
  • "workspace_groups": {
    },
  • "custom_field_values": {
    },
  • "workspace_resources": {
    },
  • "status_reports": {
    },
  • "account_colors": {
    }
}

Creating a new Workspace

This endpoint returns structured Workspace objects. As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array and will be indexed by ID in the workspaces top-level JSON key. Please see our Response Format section for more information.

Request
query Parameters
include
string

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.
  • 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.
optional_fields
Array of strings

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

Items Enum: "client_lead_name" "provider_lead_name" "stage" "estimated_minutes" "total_invoiced" "total_minutes_approved" "billable_minutes" "non_billable_minutes" "minutes_logged" "incoming_email_address" "lock_date"
Request Body schema: application/json
required
object
consultant_role_name
string

The label for the consultant team.

client_role_name
string

The label for client team.

budgeted
boolean

Whether the project is budgeted. Defaults to true for paid accounts. Defaults to false for free accounts.

start_date
string <date>

The date must be in ISO 8601 format.

due_date
string <date>

The date must be in ISO 8601 format.

description
string
currency
string

Defaults to the user's account's currency or USD. This is only relevant for a project that is budgeted. If a rate_card_id is supplied, this argument is ignored.

access_level
string

Whether the project is open, and who can join it.

Enum: "invitation" "open" "admins"
rate_card_id
integer <int32>

The rate card for the project. The rate card currency must match that of the project.

exclude_archived_stories_percent_complete
boolean

Exclude archived tasks from being used in completion percentage calculation.

tasks_default_non_billable
boolean

Defaults tasks as billable.

stories_are_fixed_fee_by_default
boolean

Defaults tasks as fixed fee.

expenses_in_burn_rate
boolean

Sets whether both expenses and invoice additional items should be included in the actual fees calculation for the project. Note that setting this field sets the values of both actual_fees_includes_expenses and actual_fees_includes_additional_line_items. To set the values individually, set actual_fees_includes_expenses and actual_fees_includes_additional_line_items instead.

actual_fees_includes_expenses
boolean

Sets whether expenses should be included in the actual fees calculation for the project.

actual_fees_includes_additional_line_items
boolean

Sets whether invoice additional items should be included in the actual fees calculation for the project.

posts_require_privacy_decision
boolean

Determines who can see communications.

status_key
integer <int32>

The status of the project. See the Knowledge Base for a list of project status IDs.

object

Allows for customizing invoices.

approver_id
integer <int32>

Determines the time approver for a project.

workspace_group_ids
Array of integers <int32>

Determines the groups to which the project belongs.

project_template_start_date
string <date>

Sets the project start date when applying a template. The date must be in ISO 8601 format.

project_template_checklist_as_todos
boolean

Whether checklist items are converted to To Dos when applying a template.

Array of objects

Assigns template resource mappings when applying a template.

project_template_weekends_as_workdays
boolean

Sets whether weekends count as work days when applying a template.

project_template_create_unnamed_resources
boolean

Converts all project template assignments with a role to unnamed resources in the project, and ignores the project_template_assignment_mappings parameter.

project_template_distribute_hours
boolean

Sets whether estimated hours are automatically added as scheduled hours for all tasks when applying a template (distributed evenly between the task start date and end date).

project_tracker_template_id
integer <int32>

Determines the template that should be used to fill the new project.

primary_workspace_group_id
integer <int32>

Determines which group is the primary group for the project.

target_margin
integer <int32>

The percentage of the cost that is profit.

object

Typically populated programmatically by a third party system via an integration, this is an optional object that holds data from an external system. It connects objects in an external system with objects in Kantata OX (for example, to connect a Jira issue to a Kantata OX Project).

account_color_id
integer <int32>

The account color ID associated with the project (optional).

Array of objects

Determines the custom field values for the project.

stage
string

The stage of the project. Options are 'estimate' and 'project'.

Enum: "estimate" "project"
title
required
string
creator_role
string

Can be either 'maven'/'consultant' (to represent the consultant role), or 'buyer'/'client' (to represent the client role). Defaults to 'maven' if not set.

Enum: "client" "consultant"
price
integer <int32>

Determines the starting budget of a project. This is required for budgeted projects.

change_orders_enabled
boolean

Toggles if the project requires change orders for some fields.

If the attribute is not explicitly passed in the create request, it defaults to true if the workspace is budgeted.

change_orders
boolean

Toggles if the project requires change orders for some fields.

If the attribute is not explicitly passed in the create request, it defaults to true if the workspace is budgeted.

Array of objects

Determines the organizations of which the project will be a part.

Array of objects

Determines the participants in the project.

primary_maven_id
integer <int32>

The user_id of the provider lead of the project.

require_expense_approvals
boolean

Requires expenses to be approved by Administrators.

require_time_approvals
boolean

Requires time entries to be approved by Administrators.

estimate_scenario_id
integer <int32>

The estimate scenario from which the project was created.

attachment_ids
Array of integers <int32>

The attachment ids for the files to be associated with the project after its created.

Responses
200

Workspace has been created.

Response Schema: application/json
count
integer <int32>
object
Array of objects
object
object
object
object
object
object
object
object
object
object
object
400

Bad Request

401

Unauthorized request

403

Forbidden request

404

Page Not Found

422

Unprocessable Entity

503

Service is unavailable

post/workspaces
Request samples
application/json
{
  • "workspace": {
    }
}
Response samples
application/json
{
  • "count": 0,
  • "meta": {
    },
  • "results": [
    ],
  • "workspaces": {
    },
  • "external_references": {
    },
  • "stories": {
    },
  • "users": {
    },
  • "participations": {
    },
  • "timesheet_submissions": {
    },
  • "workspace_groups": {
    },
  • "custom_field_values": {
    },
  • "workspace_resources": {
    },
  • "status_reports": {
    },
  • "account_colors": {
    }
}

Fetching a single Workspace

Gets a project by ID.

By default, you will receive a 404 status if you try to retrieve an archived project. Use the include_archived:true filter to retrieve an archived project.

Users with Project Lead (or lower) account permissions can retrieve projects they are not participating in if they have the All projects or All projects accessible to their organization (if Organizations are enabled) permission in the View Resource Center section of the Resource Management Access Group set.

This endpoint returns structured Workspace objects. As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array and will be indexed by ID in the workspaces top-level JSON key. Please see our Response Format section for more information.

Request
path Parameters
id
required
integer

The ID of the Model.

query Parameters
include
string

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.
  • 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.
optional_fields
Array of strings

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

Items Enum: "client_lead_name" "provider_lead_name" "stage" "estimated_minutes" "total_invoiced" "total_minutes_approved" "billable_minutes" "non_billable_minutes" "minutes_logged" "incoming_email_address" "lock_date"
Responses
200

The Workspace has been retrieved.

Response Schema: application/json
count
integer <int32>
object
Array of objects
object
object
object
object
object
object
object
object
object
object
object
400

Bad Request

401

Unauthorized request

403

Forbidden request

404

Page Not Found

422

Unprocessable Entity

503

Service is unavailable

get/workspaces/{id}
Request samples
Response samples
application/json
{
  • "count": 0,
  • "meta": {
    },
  • "results": [
    ],
  • "workspaces": {
    },
  • "external_references": {