Toggl Mcp TypeScript MCP Server

It is generated with Stainless.

Installation

Direct invocation

You can run the MCP Server directly via npx:

export TOGGL_MCP_USERNAME="My Username"
export TOGGL_MCP_PASSWORD="My Password"
npx -y toggl-mcp-mcp@latest

Via MCP Client

There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server.

For clients with a configuration JSON, it might look something like this:

{
  "mcpServers": {
    "toggl_mcp_api": {
      "command": "npx",
      "args": ["-y", "toggl-mcp-mcp", "--client=claude", "--tools=dynamic"],
      "env": {
        "TOGGL_MCP_USERNAME": "My Username",
        "TOGGL_MCP_PASSWORD": "My Password"
      }
    }
  }
}

Exposing endpoints to your MCP Client

There are two ways to expose endpoints as tools in the MCP server:

1. Exposing one tool per endpoint, and filtering as necessary
2. Exposing a set of tools to dynamically discover and invoke endpoints from the API

Filtering endpoints and tools

You can run the package on the command line to discover and filter the set of tools that are exposed by the MCP Server. This can be helpful for large APIs where including all endpoints at once is too much for your AI's context window.

You can filter by multiple aspects:

• --tool includes a specific tool by name
• --resource includes all tools under a specific resource, and can have wildcards, e.g. my.resource*
• --operation includes just read (get/list) or just write operations

Dynamic tools

If you specify --tools=dynamic to the MCP server, instead of exposing one tool per endpoint in the API, it will expose the following tools:

1. list_api_endpoints - Discovers available endpoints, with optional filtering by search query
2. get_api_endpoint_schema - Gets detailed schema information for a specific endpoint
3. invoke_api_endpoint - Executes any endpoint with the appropriate parameters

This allows you to have the full set of API endpoints available to your MCP Client, while not requiring that all of their schemas be loaded into context at once. Instead, the LLM will automatically use these tools together to search for, look up, and invoke endpoints dynamically. However, due to the indirect nature of the schemas, it can struggle to provide the correct properties a bit more than when tools are imported explicitly. Therefore, you can opt-in to explicit tools, the dynamic tools, or both.

See more information with --help.

All of these command-line options can be repeated, combined together, and have corresponding exclusion versions (e.g. --no-tool).

Use --list to see the list of available tools, or see below.

Specifying the MCP Client

Different clients have varying abilities to handle arbitrary tools and schemas.

You can specify the client you are using with the --client argument, and the MCP server will automatically serve tools and schemas that are more compatible with that client.

• --client=<type>: Set all capabilities based on a known MCP client

  • Valid values: openai-agents, claude, claude-code, cursor
  • Example: --client=cursor

Additionally, if you have a client not on the above list, or the client has gotten better over time, you can manually enable or disable certain capabilities:

• --capability=<name>: Specify individual client capabilities
  • Available capabilities:
    • top-level-unions: Enable support for top-level unions in tool schemas
    • valid-json: Enable JSON string parsing for arguments
    • refs: Enable support for $ref pointers in schemas
    • unions: Enable support for union types (anyOf) in schemas
    • formats: Enable support for format validations in schemas (e.g. date-time, email)
    • tool-name-length=N: Set maximum tool name length to N characters
  • Example: --capability=top-level-unions --capability=tool-name-length=40
  • Example: --capability=top-level-unions,tool-name-length=40

Examples

1. Filter for read operations on cards:

--resource=cards --operation=read

2. Exclude specific tools while including others:

--resource=cards --no-tool=create_cards

3. Configure for Cursor client with custom max tool name length:

--client=cursor --capability=tool-name-length=40

4. Complex filtering with multiple criteria:

--resource=cards,accounts --operation=read --tag=kyc --no-tool=create_cards

Importing the tools and server individually

// Import the server, generated endpoints, or the init function
import { server, endpoints, init } from "toggl-mcp-mcp/server";

// import a specific tool
import fetchAuditLogs from "toggl-mcp-mcp/tools/audit-logs/fetch-audit-logs";

// initialize the server and all endpoints
init({ server, endpoints });

// manually start server
const transport = new StdioServerTransport();
await server.connect(transport);

// or initialize your own server with specific tools
const myServer = new McpServer(...);

// define your own endpoint
const myCustomEndpoint = {
  tool: {
    name: 'my_custom_tool',
    description: 'My custom tool',
    inputSchema: zodToJsonSchema(z.object({ a_property: z.string() })),
  },
  handler: async (client: client, args: any) => {
    return { myResponse: 'Hello world!' };
  })
};

// initialize the server with your custom endpoints
init({ server: myServer, endpoints: [fetchAuditLogs, myCustomEndpoint] });

Available Tools

The following tools are available in this MCP server.

Resource audit_logs:

• fetch_audit_logs (read): Returns a list of audit log events for the specified organization and time range.

Resource auth.saml2.login:

• handle_callback_saml2_auth_login (write): Receives the IdP Callback containing the SAML2 assertion with response of user authentication in the IdP.
• retrieve_url_saml2_auth_login (read): Returns the SSO URL given an email address for authenticating in an Identity Provider.

Resource avatars:

• create_avatars (write): Handles POST avatar requests.
• delete_avatars (write): Handles DELETE avatar requests.
• use_gravatar_avatars (write): Change user avatar to gravatar.

Resource countries:

• list_countries (read): Returns a list of existing countries
• retrieve_subdivisions_countries (read): Returns a list of subdivisions for a specific country.

Resource currencies:

• list_currencies (read): Returns a list of available currencies.

Resource desktop_login:

• retrieve_desktop_login (read): Store new desktop login token

Resource desktop_login_tokens:

• create_desktop_login_tokens (write): Store new desktop login token

Resource feedback:

• send_feedback (write): Send Feedback

Resource ical:

• retrieve_workspace_user_ical (read): Returns ical file with TEs from last 14 days

Resource integrations.calendar:

• update_integrations_calendar (write): Updates an integration properties.
• list_integrations_calendar (read): Get all integrations a user has. Each user may have at most one integration per provider.
• delete_integrations_calendar (write): Executes logic deletion of an integration.
• setup_integrations_calendar (read): Set up an integration with a given provider, returning a URL to the said provider in order to

Resource integrations.calendar.calendars:

• list_calendar_integrations_calendars (read): Get all calendars for a given user that was previously saved in the database.
• list_events_deprecated_calendar_integrations_calendars (read): Get all events for a given calendar in a given integration.
• list_for_integration_calendar_integrations_calendars (read): Get all calendars for a given integration that was previously saved in the database.
• list_selected_calendar_integrations_calendars (read): Get all selected calendars for a given user that was previously saved in the database.
• update_all_calendar_integrations_calendars (write): This endpoint uses the passed integration to get a provider and update all the calendars from that
• update_selection_calendar_integrations_calendars (write): This endpoint is used to set updatable fields of a calendar like selected field.

Resource integrations.calendar.events:

• list_calendar_integrations_events (read): Get all events from selected calendars for the caller user. This endpoint will only return events if events were fetched from provider before the request is made. Check which is the endpoint for the events.
• update_all_calendar_integrations_events (write): Fetch all events from a user's selected calendars and save in database.

Resource integrations.calendar.events.details_suggestion:

• create_events_calendar_integrations_details_suggestion (write): Given one or more event IDs, this endpoint responds with the most probable event details (and its accuracy) to assign to the to-be-created time entry for each event ID. This endpoint will only suggests time entries with description and project not empty, because it uses the description to tell if the TE is similar and the project as the main detail to be suggested.

  If the description is equal, as well as all the other details, the accuracy will be 100%, in the case the description is equal but the other details differs, the most frequent will be suggested and the accuracy will be given based on the frequency. In the case there is no TE with the same description the most similar will be suggested based on the Jaro-Winkler algorithm, and the accuracy will be the similarity rating.

  This endpoint returns status 200 OK with only the successful suggestions. Any event ID that is invalid or the user does not have access to will be ignored, as well as any event that has no available suggestion.

• retrieve_events_calendar_integrations_details_suggestion (read): Given an event ID, this endpoint responds with the most probable event details (and the accuracy) to assign to the to-be-created time entry. This endpoint will only suggests time entries with description and project not empty, because it uses the description to tell if the TE is similar and the project as the main detail to be suggested.

  If the description is equal, as well as all the other details, the accuracy will be 100%, in the case the description is equal but the other details differs, the most frequent will be suggested and the accuracy will be given based on the frequency. In the case there is no TE with the same description the most similar will be suggested based on the Jaro-Winkler algorithm, and the accuracy will be the similarity rating.

  This endpoint returns status 200 OK and a "null" string in case no suggestion was found.

Resource invitations:

• retrieve_invitations (read): Returns an invitation data by code.

Resource keys:

• retrieve_keys (read): Returns the current JWKS keyset used to sign JWT tokens.

Resource me:

• retrieve_me (read): Returns details for the current user.
• update_me (write): Updates details for the current user.
• accept_tos_me (write): Accepts the last version of the Terms of Service for the current user.
• check_logged_me (read): Used to check if authentication works.
• close_account_me (write): Close Account
• disable_product_emails_me (write): Disable product emails.
• disable_weekly_report_me (write): Disable weekly report.
• enable_sso_me (write): Confirm SSO enabling in existing Toggl account after successful SSO
• get_location_me (read): Returns the client's IP-based location. If no data is present, empty response will be yielded.
• get_quota_me (read): Returns the API quota for the current user for all the organizations they are part of.
• get_time_entries_shared_with_me (write): Get the sharing details of the specified time entries in bulk
• get_web_timer_me (read): Get web timer.
• list_clients_me (read): Get Clients.
• list_features_me (read): Get features.
• list_organizations_me (read): Get all organizations a given user is part of.
• list_tags_me (read): Returns tags for the current user.
• list_tasks_me (read): Returns tasks from projects in which the user is participating.
• list_timesheets_me (read): Returns the timehseets for the current user.
• list_track_reminders_me (read): Returns a list of track reminders.
• list_workspaces_me (read): Lists workspaces for given user.
• reset_token_me (write): Resets API token for the current user.

Resource me.export:

• create_me_export (write): An object which data to be downloaded for an user
• list_me_export (read): List of objects to be downloaded for an user

Resource me.export.data:

• retrieve_export_me_data (read): Get a zip file List of download requests from an user.

Resource me.favorites:

• create_me_favorites (write): This endpoint allows the creation of a favorite given some parameters. The workspace is required, as well as either description or project (no favorite without both will be accepted). The user is also required, but it already goes in the authentication. Also, the user must have access to all resources being referenced in the favorite attributes, and these resources should have valid relationships. For instance, if you want a favorite in a given workspace and with some tags, the tags must belong to that workspace. In case of user having no access to an attribute, a 403 status is returned, if the attributes don't relate correctly between themselves the status returned will be 400.
• update_me_favorites (write): This endpoint allows updating an array of favorites. It follow all the requirements and behavior from the [post] (Create Favorite) counterpart.
• list_me_favorites (read): Gets all favorites for the requesting user
• delete_me_favorites (write): Deletes a given favorite logically from database, as well as its tags.
• suggest_me_favorites (write): It will create 3 favorites based on past user's TE activity and return them. Suggested favorites will be created only once for a given user, and only if the user has never created a favorite before (either manually or by a previous suggestion request). If there is no past TE data there won't be suggested favorites either.

Resource me.flags:

• list_me_flags (read): Returns flags for the current user. They will be represented by an object with dynamic string keys, where the value can be of any type.
• add_me_flags (write): Add flags for the current user. The current limits are 4 flags per request, 128 flags in total. Keys and values can be up to 32 and 64 characters, respectively.

Resource me.preferences:

• retrieve_me_preferences (read): Returns user preferences and alpha features. The list of alpha features contains a full list of feature codes (every feature that exists in database) and the enabled flag specifying if that feature should be enabled or disabled for the user.
• update_me_preferences (write): With this endpoint, preferences can be modified and alpha features can be enabled or disabled.
• retrieve_for_client_me_preferences (read): Returns user preferences and alpha features. The list of alpha features contains a full list of feature codes (every feature that exists in database) and the enabled flag specifying if that feature should be enabled or disabled for the user.
• update_for_client_me_preferences (write): With this endpoint, preferences can be modified and alpha features can be enabled or disabled.

Resource me.projects:

• list_me_projects (read): Get projects
• list_paginated_me_projects (read): Get paginated projects.

Resource me.push_services:

• list_me_push_services (read): Get list of firebase tokens registered for current user.
• register_me_push_services (write): Register Firebase token for current user
• unregister_me_push_services (write): Unregister Firebase token for current user

Resource me.time_entries:

• retrieve_me_time_entries (read): Load time entry by ID that is accessible by the current user.
• list_me_time_entries (read): Lists latest time entries.
• checklist_me_time_entries (read): Check the needed time entries requirement to offer coupon to user
• current_me_time_entries (read): Load running time entry for user ID.

Resource organizations:

• create_organizations (write): Creates a new organization with a single workspace and assigns current user as the organization owner
• retrieve_organizations (read): Returns organization name and current pricing plan
• update_organizations (write): Updates an existing organization
• list_payment_records_organizations (read): Returns paid invoices
• list_roles_organizations (read): Returns a list of organization specific and global roles.

Resource organizations.invitations:

• create_organizations_invitations (write): Creates a new invitation for the user.
• accept_organizations_invitations (write): User connected with invitation is marked as joined, email is sent to the inviter.
• reject_organizations_invitations (write): User connected with invitation is marked as deleted.
• resend_organizations_invitations (write): Resend invitation email to user.

Resource organizations.groups:

• create_organizations_groups (write): Creates a group in the specified organization
• update_organizations_groups (write): Edits a group in the specified organization
• list_organizations_groups (read): Returns list of groups in organization based on set of url parameters. List is sorted by name.
• delete_organizations_groups (write): Deletes a group from the specified organization
• patch_organizations_groups (write): Patches a group in the specified organization. Patches are applied individually.

Resource organizations.invoices:

• retrieve_pdf_organizations_invoices (read): Returns a Invoice document in PDF form.

Resource organizations.owner:

• retrieve_organizations_owner (read): Returns organization owner data.

Resource organizations.owner.transfer:

• create_owner_organizations_transfer (write): Return the ownership transfer for a given organization.
• retrieve_owner_organizations_transfer (read): Returns single organization transfer in the organization
• update_owner_organizations_transfer (write): Return the ownership transfer for a given organization and emails stakeholders.
• list_owner_organizations_transfer (read): Returns list of organization transfers made in the organization

Resource organizations.plans:

• retrieve_organizations_plans (read): Returns pricing plan for an organization identified by plan_id
• list_organizations_plans (read): Returns pricing plans for an organization

Resource organizations.segmentation:

• retrieve_organizations_segmentation (read): Returns organization segmentation information
• update_organizations_segmentation (write): Save organization segmentation information

Resource organizations.subscription:

• create_organizations_subscription (write): Allows to create a new unified subscription for an organization.
• retrieve_organizations_subscription (read): Returns subscription data.
• update_organizations_subscription (write): Allows to update existing unified subscription for an organization.
• apply_referral_bonus_organizations_subscription (write): Applies the Referral Bonus if the customer is elligible
• cancel_organizations_subscription (write): Cancels an existing subscription.
• create_cancellation_feedback_organizations_subscription (write): Allows to create a cancellation feedback for an organization subscription.
• create_discount_request_organizations_subscription (write): Endpoint for client's feedback when canceling plan. It triggers an e-mail to support with feedbacks and discount request.
• create_setup_intent_organizations_subscription (write): Create a setup intent for collecting customer's payment method for future payments
• create_trial_organizations_subscription (write): Allows to create a new unified subscription on initial 30-day trial for an organization.
• get_feature_upsell_multi_organizations_subscription (write): Gets feature upsell information for all organizations the user has access to
• request_upgrade_organizations_subscription (write): Endpoint for triggering a call to action on admins for upgrading their subscription.
• retrieve_invoice_summary_organizations_subscription (read): Returns a summary of the next invoice for an Organization
• retrieve_payment_failed_organizations_subscription (read): Returns subscription payment failed details.

Resource organizations.subscription.customer:

• create_subscription_organizations_customer (write): Creates unified customer for organization.
• retrieve_subscription_organizations_customer (read): Retrieve unified customer belonging to the organization.
• update_subscription_organizations_customer (write): Allows to update unified customer data. Customer name, email, country & postal code are mandatory fields. Optional fields will be cleared if they don't have a value.

Resource organizations.subscription.promocode:

• apply_subscription_organizations_promocode (write): Applies the given promotion code to organization's customer If the customer already has the promotion code, then it will be overridden
• remove_subscription_organizations_promocode (write): Removes any discount (promotion code) applied to the organization's customer

Resource organizations.subscription.purchase_orders:

• retrieve_pdf_subscription_organizations_purchase_orders (read): Returns a Purchase Order document in PDF form.

Resource organizations.users:

• update_organizations_users (write): Changes a single organization-user. Can affect the following values:
• list_organizations_users (read): Returns list of users in organization based on set of url parameters: Result is paginated. Pagination params are returned in headers
• bulk_update_organizations_users (write): Apply changes in bulk to users in an organization (currently deletion only).
• leave_organizations_users (write): Leaves organization, effectively delete user account in org and delete organization if it is last user
• list_detailed_organizations_users (read): Returns list of users in organization based on set of url parameters: Result is paginated. Pagination params are returned in headers

Resource organizations.workspaces:

• create_organizations_workspaces (write): Create a workspace within an existing organization.
• list_groups_organizations_workspaces (read): Returns list of groups in a workspace based on set of url parameters. List is sorted by name.
• retrieve_statistics_organizations_workspaces (read): Returns map indexed by workspace ID where each map element contains workspace admins list, members count and groups count.
• update_assignments_organizations_workspaces (write): Assign or remove users to/from a workspace or to/from groups belonging to said workspace.

Resource organizations.workspaces.workspace_users:

• update_workspaces_organizations_workspace_users (write): Changes the users in a workspace (currently deletion only).
• list_workspaces_organizations_workspace_users (read): Returns any users who belong to the workspace directly or through at least one group.

Resource smail:

• send_contact_email_smail (write): Send an email to a contact
• send_demo_email_smail (write): Send an email for a demo
• send_meet_email_smail (write): Send an email for meet with message and location

Resource status:

• retrieve_status (read): Returns API status.

Resource subscriptions:

• list_plans_subscriptions (read): Get all available plans along with all features available per plan.

Resource sync_server.me:

• list_goals_sync_server_me (read): Gets all goals for the requesting user.

Resource timeline:

• create_timeline (write): Save timeline events and returns timeline settings
• retrieve_timeline (read): Get timeline events
• delete_timeline (write): Delete all timeline data for the current user

Resource timezones:

• list_timezones (read): Returns known timezones.
• list_with_offsets_timezones (read): Returns known timezones with their offsets.

Resource workspaces:

• retrieve_workspaces (read): Get information of single workspace.
• update_workspaces (write): Update a specific workspace.
• list_currencies_workspaces (read): Get the currencies for a given workspace.
• list_plans_workspaces (read): Lists Public subscription plans.
• retrieve_statistics_workspaces (read): Returns workspace admins list, members count and groups count

Resource workspaces.alerts:

• create_workspaces_alerts (write): Handles POST alert requests.
• update_workspaces_alerts (write): Handles PUT alert requests.
• list_workspaces_alerts (read): Returns a list of existing alerts
• delete_workspaces_alerts (write): Handles DELETE alert requests.

Resource workspaces.clients:

• create_workspaces_clients (write): Create workspace client.

• retrieve_workspaces_clients (read): Load client from workspace.

• update_workspaces_clients (write): Update workspace client.

  Note: use /workspaces/{workspace_id}/clients/{client_id}/archive to archive the client and /workspaces/{workspace_id}/clients/{client_id}/restore to restore it.

• list_workspaces_clients (read): List clients from workspace.

• delete_workspaces_clients (write): Delete workspace client.

• archive_workspaces_clients (write): Archives a workspace client and related projects. Only for premium workspaces.

• archive_bulk_workspaces_clients (write): Archives workspace clients and related projects. Only for premium workspaces.

• delete_bulk_workspaces_clients (write): Delete one or more workspace clients.

• list_by_ids_workspaces_clients (write): List clients from workspace by client_ids

• restore_workspaces_clients (write): Restores client and all related or specified projects from the given workspace.

Resource workspaces.dashboard:

• list_all_activity_workspaces_dashboard (read): Dashboard's main purpose is to give an overview of what users in the workspace are doing and have been doing. The activity object holds the data of 20 latest actions in the workspace or latest activity for every workspace user. Activity object has the following properties
  • user_id: user ID
  • project_id: project ID (ID is 0 if time entry doesn't have project connected to it)
  • duration: time entry duration in seconds. If the time entry is currently running, the duration attribute contains a negative value, denoting the start of the time entry in seconds since epoch (Jan 1 1970). The correct duration can be calculated as current_time + duration, where current_time is the current time in seconds since epoch.
  • description: (Description property is not present if time entry description is empty)
  • stop: time entry stop time (ISO 8601 date and time. Stop property is not present when time entry is still running)
  • tid: task id, if applicable
• list_most_active_workspaces_dashboard (read): Dashboard's main purpose is to give an overview of what users in the workspace are doing and have been doing. The most active user object holds the data of the top 5 users who have tracked the most time during last 7 days. Most active user object has the following properties
  • user_id: user ID
  • duration: Sum of time entry durations that have been created during last 7 days.
• list_top_activity_workspaces_dashboard (read): Dashboard's main purpose is to give an overview of what users in the workspace are doing and have been doing. Return objects are same as with the /workspaces/{workspace_id}/dashboard/all_activity request.

Resource workspaces.expenses:

• list_workspaces_expenses (read): Get work expenses.
• upload_workspaces_expenses (write): Upload a work expense.

Resource workspaces.exports:

• create_workspaces_exports (write): List of workspaces downloaded from a given workspace.
• list_workspaces_exports (read): List of workspace download requests from a given workspace.

Resource workspaces.exports.data:

• retrieve_exports_workspaces_data (read): Send a zip file List of workspace download requests from a given workspace.

Resource workspaces.favorites:

• create_workspaces_favorites (write): This endpoint allows the creation of a favorite. Also, the user must have access to all resources being referenced in the favorite attributes, and these resources should have valid relationships. For instance, if you want a favorite in a given workspace and with some tags, the tags must belong to that workspace. In case of user having no access to an attribute, a 403 status is returned, if the attributes don't relate correctly between themselves the status returned will be 400.
• update_workspaces_favorites (write): This endpoint allows updating an array of favorites. It follow all the requirements and behavior from the [post] (Create Favorite) counterpart.
• list_workspaces_favorites (read): Gets all favorites for the requesting user
• delete_workspaces_favorites (write): Deletes a given favorite logically from database, as well as its tags.
• suggest_workspaces_favorites (write): It will create 3 favorites based on past user's TE activity and return them. Suggested favorites will be created only once for a given user, and only if the user has never created a favorite before (either manually or by a previous suggestion request). If there is no past TE data there won't be suggested favorites either.

Resource workspaces.goals:

• create_workspaces_goals (write): Create a Goal object with its parameters.
• retrieve_workspaces_goals (read): Gets a goal that relates to the calling user in the specified workspace.
• update_workspaces_goals (write): Update a goal with the updatable parameters given by UpdatePayload
• list_workspaces_goals (read): Gets all goals for the requesting user in the workspace.
• delete_workspaces_goals (write): Delete a goal that was created by the calling user

Resource workspaces.groups:

• create_workspaces_groups (write): Creates a group in the specified workspace
• update_workspaces_groups (write): Updates the group.
• list_workspaces_groups (read): Returns a list of groups for the specified workspace.
• delete_workspaces_groups (write): Deletes the group.

Resource workspaces.ical:

• reset_workspaces_ical (write): Reset the iCal token for a given workspace.
• toggle_workspaces_ical (write): Toggle the iCal token on/off for a given workspace.

Resource workspaces.invoices:

• create_workspaces_invoices (write): Creates new user invoice.
• list_workspaces_invoices (read): Get invoices for given workspace with pagination.
• delete_workspaces_invoices (write): Deletes user invoice by ID if exists.
• retrieve_pdf_workspaces_invoices (read): Returns an Invoice document in PDF form.

Resource workspaces.linked_sso_profiles:

• list_workspaces_linked_sso_profiles (read): Returns a list of SSO profiles that are linked to the given workspace.
• link_workspaces_linked_sso_profiles (write): Link the workspace with the given ID to an SSO profile with the given ID.
• unlink_workspaces_linked_sso_profiles (write): Unlink the workspace from an SSO profile.

Resource workspaces.logo:

• retrieve_workspaces_logo (read): Get the logo for a given workspace.
• delete_workspaces_logo (write): Delete the logo for a given workspace.
• upload_workspaces_logo (write): Post the logo for a given workspace.

Resource workspaces.payment_receipts:

• retrieve_pdf_workspaces_payment_receipts (read): Returns payment receipt pdf file.

Resource workspaces.preferences:

• retrieve_workspaces_preferences (read): Get the preferences for a given workspace.
• update_workspaces_preferences (write): Update the preferences for a given workspace.

Resource workspaces.project_groups:

• create_workspaces_project_groups (write): Adds group to project for given workspace.
• list_workspaces_project_groups (read): Get project groups for given workspace.
• delete_workspaces_project_groups (write): Remove project group for a given workspace.

Resource workspaces.project_users:

• update_workspaces_project_users (write): Update the data for a project user for a given workspace.
• list_workspaces_project_users (read): List all projects users for a given workspace.
• delete_workspaces_project_users (write): Delete a project user for a given workspace.
• add_workspaces_project_users (write): Include a project user for a given workspace.
• list_paginated_workspaces_project_users (write): List projects users for a given workspace and set of project IDs paginated.
• patch_workspaces_project_users (write): Patch a list of project users for a given workspace.

Resource workspaces.projects:

• create_workspaces_projects (write): Create project for given workspace.
• retrieve_workspaces_projects (read): Get project for given workspace.
• update_workspaces_projects (write): Update project for given workspace.
• list_workspaces_projects (read): Get projects for given workspace.
• delete_workspaces_projects (write): Delete project for given workspace.
• get_billable_amounts_workspaces_projects (write): Get projects billable amounts
• get_periods_workspaces_projects (read): Get recurring project periods for given workspace.
• get_statistics_workspaces_projects (read): Get statistics for given workspace and project. For time entry related information, this endpoint does not consider running ones.
• get_task_count_workspaces_projects (write): Retrieves the task count for the specified projects
• get_templates_workspaces_projects (read): Get projects templates for given workspace.
• get_user_count_workspaces_projects (write): Retrieves the user count for the specified projects
• pin_workspaces_projects (write): Pin or unpin a project to top of user's project list
• update_bulk_workspaces_projects (write): Bulk editing workspace projects.

Resource workspaces.projects.tasks:

• create_projects_workspaces_tasks (write): Post project tasks for given workspace.
• retrieve_projects_workspaces_tasks (read): Get project task for given task id.
• update_projects_workspaces_tasks (write): Put project task for given workspace.
• list_projects_workspaces_tasks (read): Get project tasks for given workspace.
• delete_projects_workspaces_tasks (write): Delete projects task for given workspace.
• update_bulk_projects_workspaces_tasks (write): Patch project tasks for given workspace.

Resource workspaces.rates:

• create_workspaces_rates (write): Creates a new rate.
• retrieve_workspaces_rates (read): Get rates by level(workspace|project|task|user).

Resource workspaces.reports.shared:

• create_reports_workspaces_shared (write): Add shared report.
• retrieve_reports_workspaces_shared (read): Get a saved report.
• update_reports_workspaces_shared (write): Change shared report.
• list_reports_workspaces_shared (read): Get shared report.
• bulk_delete_reports_workspaces_shared (write): Bulk delete saved reports.
• delete_report_reports_workspaces_shared (write): Delete saved report.
• update_report_reports_workspaces_shared (write): Change saved report.

Resource workspaces.scheduled_reports:

• create_workspaces_scheduled_reports (write): Endpoint for setting up a scheduled report.
• list_workspaces_scheduled_reports (read): Lists scheduled reports.
• delete_workspaces_scheduled_reports (write): Endpoint for delete a scheduled report.

Resource workspaces.subscription:

• retrieve_workspaces_subscription (read): Returns subscription data.

Resource workspaces.subscription.purchase_orders:

• retrieve_pdf_subscription_workspaces_purchase_orders (read): Returns a Purchase Order document in PDF form.

Resource workspaces.tags:

• create_workspaces_tags (write): Create workspace tags.
• update_workspaces_tags (write): Update workspace tags.
• list_workspaces_tags (read): List Workspace tags.
• delete_workspaces_tags (write): Delete workspace tags.
• bulk_delete_workspaces_tags (write): Patch will not be executed if there are errors with some records.

Resource workspaces.tasks:

• list_workspaces_tasks (read): List Workspace tasks.
• list_basic_workspaces_tasks (read): List Workspace tasks.
• list_by_project_ids_workspaces_tasks (write): List tasks from workspace by project_ids

Resource workspaces.time_entries:

• create_workspaces_time_entries (write): Creates a new workspace TimeEntry.
• update_workspaces_time_entries (write): Updates a workspace time entry.
• delete_workspaces_time_entries (write): Deletes a workspace time entry.
• stop_workspaces_time_entries (write): Stops a workspace time entry.
• update_bulk_workspaces_time_entries (write): In short: http://tools.ietf.org/html/rfc6902 and http://tools.ietf.org/html/rfc6901 with some additions. Patch will be executed partially when there are errors with some records. No transaction, no rollback.

Resource workspaces.time_entry_constraints:

• create_workspaces_time_entry_constraints (write): Post the time entry constraints for a given workspace.
• retrieve_workspaces_time_entry_constraints (read): Get the time entry constraints for a given workspace.

Resource workspaces.time_entry_invitations:

• list_workspaces_time_entry_invitations (read): Get invitations for time entries
• respond_workspaces_time_entry_invitations (write): Accept or reject an invitation for a time entry

Resource workspaces.timesheet_setups:

• create_workspaces_timesheet_setups (write): Create timesheet setups.
• update_workspaces_timesheet_setups (write): Updates a timesheet setups.
• list_workspaces_timesheet_setups (read): Get timesheet setups for a given workspace.
• delete_workspaces_timesheet_setups (write): Delete a timesheet setup for a given workspace.

Resource workspaces.timesheets:

• update_workspaces_timesheets (write): Updates a timesheet.
• list_workspaces_timesheets (read): Get timesheets applying various filters.
• get_hours_workspaces_timesheets (write): Get timesheet working hours and total tracked seconds.
• get_time_entries_workspaces_timesheets (read): Get the time entries from within a timesheet timeframe.
• update_batch_workspaces_timesheets (write): Updates a batch of timesheets.

Resource workspaces.track_reminders:

• create_workspaces_track_reminders (write): Creates a workspace tracking reminder.
• update_workspaces_track_reminders (write): Updates a workspace tracking reminder.
• list_workspaces_track_reminders (read): Returns a list of track reminders.
• delete_workspaces_track_reminders (write): Deletes a workspace tracking reminder.

Resource workspaces.users:

• update_workspaces_users (write): Update the data for a user in a given workspace.
• list_workspaces_users (read): List all users for a given workspace.
• get_data_workspaces_users (write): List of the specified workspace users basic data for a given workspace.

Resource workspaces.workspace_users:

• update_workspaces_workspace_users (write): Update the data for a workspace_user in a given workspace.
• list_workspaces_workspace_users (read): List all workspace_users for a given workspace.
• delete_workspaces_workspace_users (write): Removes user from workspace