Dovkie
Sign in
Back to monitors

asana

Asana API

REST
OpenAPI (YAML)
https://raw.githubusercontent.com/Asana/openapi/master/defs/asana_oas.yaml
Additive AI classification

Add data_retention_policy actor type to events API

The actor_type enum in the events API response now includes a new data_retention_policy value alongside existing values like user, asana, asana_support, anonymous, and external_administrator. This is a backward-compatible addition that allows clients to handle events triggered by data retention policies.

Alert history

  • Additive

    Add data_retention_policy actor type to events API

    The actor_type enum in the events API response now includes a new data_retention_policy value alongside existing values like user, asana, asana_support, anonymous, and external_administrator. This is a backward-compatible addition that allows clients to handle events triggered by data retention policies.

  • Additive

    Add AI Studio usage API with credit utilization and seats endpoints

    Two new endpoints (GET /workspaces/{workspace_gid}/ai_studio/runs and GET /workspaces/{workspace_gid}/ai_studio/seats) provide admin-only programmatic access to AI Studio usage metrics, along with four new schema types (AiStudioRunCompact, AiStudioRunResponse, AiStudioSeatCompact, AiStudioSeatResponse). This is purely additive and only available to service accounts in organizations licensed for AI Studio.

  • Breaking

    Get portfolio items response type widened to include portfolios

    The response data array for the "get portfolio items" endpoint changed from ProjectCompact to the new PortfolioItemCompact schema, which is an anyOf union of ProjectCompact and PortfolioCompact. This is technically additive (items can now be either projects or portfolios), but clients typed against ProjectCompact will break when they receive a PortfolioCompact object. Additionally, the opt_fields enum for this endpoint was drastically reduced — many previously valid field names (e.g. archived, custom_fields, members, permalink_url, etc.) were removed, which will break any client passing those field names in the query parameter.

  • Informational

    Time tracking API docs: add-on requirements clarification

    Documentation for time tracking endpoints and fields now clarifies that certain features require the Timesheets and Budgets add-on and will return 402 Payment Required if accessed without it. The fields billable_status, description, and categories in time tracking entry operations are explicitly documented as requiring this add-on. Three endpoints (POST/PUT/DELETE on time tracking entries) now document this access requirement in their descriptions and include the 402 error code in responses.

  • Informational

    Expand timesheet date requirement documentation

    Documentation for timesheet week date fields (start_date and end_date) has been clarified to indicate support for both Monday-to-Sunday and Sunday-to-Saturday week patterns. This is a documentation clarification of existing API behavior—no breaking changes to request/response formats or validation logic.

  • Breaking

    Remove 'expired' enum value from token status; add ai_studio_division_gid param

    Two changes in this diff: 1. The expired value has been removed from the enum of what appears to be a token-status string parameter/field. Any client that sends or expects "expired" as a valid status will break. 2. A new optional query parameter ai_studio_division_gid (division_gid) has been added to scope AI Studio results to a single division's GID, defaulting to the org's first licensed division when omitted — this is a purely additive change.

  • Additive

    Add AI Studio query parameters for date range and state filtering

    Three new optional query parameters have been added to the Asana API: start_at and end_at for filtering AI Studio runs by usage timestamp, and state for filtering seats by state (active, revoked, or expired). These are purely additive optional parameters that do not affect existing integrations.

  • Additive

    Add 10 new RBAC role permissions and typeahead actor/agent types

    The diff adds 10 new boolean permission fields to the RbacRoleBase schema (share_teams_with_org, create_goal, create_project, create_read_only_link, create_portfolio, view_public_teams, view_shared_with_org_projects, view_shared_with_org_tasks, view_shared_with_org_portfolios) and extends the typeahead /workspaces/{workspace_gid}/typeahead endpoint to support two new resource_type values: agent (AI Teammates) and actor (combined users and agents). All changes are additive with code examples added for documentation.

  • Additive

    Add relevance sort option to search endpoints

    Two Asana API search endpoints now accept an additional relevance value for the sort_by query parameter. This is an opt-in addition that does not affect existing integrations, as modified_at remains the default sort order.

  • Breaking

    Remove `team` field from duplicate project request body

    The team field has been removed from the request body for duplicating a project. Clients that pass team to override the destination team when duplicating a project will no longer have that parameter documented or accepted, potentially breaking workflows that rely on assigning duplicated projects to a different team.

  • Informational

    Clarified portfolio filtering behavior for service accounts

    Documentation for the GET /portfolios endpoint was expanded to clarify filtering behavior across different API user types (regular users vs. service accounts). The underlying API behavior is unchanged; this is a documentation clarification explaining how the existing owner parameter works with service accounts.

  • Additive

    Add reference custom field type and enum constraints

    The diff adds reference as a new allowed custom field type to the type enum in two schema definitions and expands the input_restrictions field with an enum constraint listing the valid reference types (task, project, portfolio, goal). These changes are purely additive: the reference type is now supported alongside existing types, and the input_restrictions array now has additional schema validation that documents what values clients can expect.

  • Informational

    Documentation updates for agents endpoint

    Updated the OpenAPI schema whitelist to include AgentCompact and AgentResponse types, and fixed a line break in the description of the GET /agents endpoint. These are documentation and schema configuration changes that do not affect the actual API behavior or client integration.

  • Additive

    Add Agents API with AI Teammates support

    New Agents resource and endpoints added to support AI Teammates. Includes two new endpoints (GET /workspaces/{workspace_gid}/agents and GET /agents/{agent_gid}), new AgentCompact and AgentResponse schemas, new create_and_edit_ai_teammates permission in RBAC roles, and expanded typeahead support with agent and actor resource types. All changes are backward-compatible additions.