[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXMWIelUotCY4_oD9-_hKhYPgRnwgm-NMgx5CqLlwOes":3,"$f8EkANX8sw95LI1Nq2K5DycQAjHr1fVArcBiP1jxaQr8":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"asana-openapi","Asana API","asana","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FAsana\u002Fopenapi\u002Fmaster\u002Fdefs\u002Fasana_oas.yaml",{"id":13,"contentHash":14,"fetchedAt":15},"01KWERTAM05XGKJSZ3B3WB8JMZ","0592cd896d2cb52f5a01393c0f86258ead9e896b769780c5891e2375aa4a5150","2026-07-01T12:00:17.849Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KWZCZ4DZCJNVZYVADBF0AH93","2f541dc34c71323d476b788b06d8f5b2b59eb0b84d1d05373c8e1b1b0cbb5659","2026-07-07T23:00:17.744Z",null,{"alerts":22},[23,30,36,44,52,59,66,73,80,87,94,101,108,115],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KWZCZ80TD2GGQQTQGFQ8CKAV","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.","2026-07-07T23:00:22.170Z","2026-07-07-add-data-retention-policy-actor-type-to-events-api",{"id":31,"severity":25,"title":32,"summary":33,"contentHash":14,"detectedAt":34,"slug":35},"01KWERTEZ1SQ8WAV0VEKKPM61Z","Add AI Studio usage API with credit utilization and seats endpoints","Two new endpoints (`GET \u002Fworkspaces\u002F{workspace_gid}\u002Fai_studio\u002Fruns` and `GET \u002Fworkspaces\u002F{workspace_gid}\u002Fai_studio\u002Fseats`) 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.","2026-07-01T12:00:23.009Z","2026-07-01-add-ai-studio-usage-api-with-credit-utilization-and-seats",{"id":37,"severity":38,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KVY181TTPS0Y6QM3Q2KCRFEY","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.","efaeb8c216fa199fbb6d796631fa93538084716a7a3c0ff04da4b72dfa5c3616","2026-06-25T00:00:31.578Z","2026-06-25-get-portfolio-items-response-type-widened-to-include",{"id":45,"severity":46,"title":47,"summary":48,"contentHash":49,"detectedAt":50,"slug":51},"01KVR0ZEFJNHYRT405CSQH9YEP","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\u002FPUT\u002FDELETE on time tracking entries) now document this access requirement in their descriptions and include the `402` error code in responses.","e894e90415893e8d17a56523f89f7cdb3a0843290389e9e637edcfdeb0959f96","2026-06-22T16:00:23.026Z","2026-06-22-time-tracking-api-docs-add-on-requirements-clarification",{"id":53,"severity":46,"title":54,"summary":55,"contentHash":56,"detectedAt":57,"slug":58},"01KVEBZMW3CHEAFWRHENCNJPRV","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\u002Fresponse formats or validation logic.","04b96047e763b4bc3440845a5c35b9de909ee6dd9cbcf4dbd54395e6641601ef","2026-06-18T22:00:19.587Z","2026-06-18-expand-timesheet-date-requirement-documentation",{"id":60,"severity":38,"title":61,"summary":62,"contentHash":63,"detectedAt":64,"slug":65},"01KV9AM86NF9CGH3GGWECR92WF","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\u002Ffield. 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.","480d289cd5c715c0c0c236ed214205c454b3161b6269ea3e384f2e6ad33da5b7","2026-06-16T23:00:25.429Z","2026-06-16-remove-expired-enum-value-from-token-status-add-ai-studio",{"id":67,"severity":25,"title":68,"summary":69,"contentHash":70,"detectedAt":71,"slug":72},"01KV6R7BD5AXGE2C1HRGQ9P00R","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.","0d66da06af013a4ff21d694afec6784c33d1cf51e064d95fc4bb11bdfa03fbf9","2026-06-15T23:00:19.493Z","2026-06-15-add-ai-studio-query-parameters-for-date-range-and-state",{"id":74,"severity":25,"title":75,"summary":76,"contentHash":77,"detectedAt":78,"slug":79},"01KTW0X6PFX9F9EW2TP8AJJ2DG","Add 10 new RBAC role permissions and typeahead actor\u002Fagent 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 `\u002Fworkspaces\u002F{workspace_gid}\u002Ftypeahead` 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.","50705f125ecdacd17d30ab498709f3da54ba5a9426a1e4a05b494ff56481eb2f","2026-06-11T19:00:25.423Z","2026-06-11-add-10-new-rbac-role-permissions-and-typeahead-actor-agent",{"id":81,"severity":25,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KT4VANVKCA27JBZ7N361KV9R","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.","6b98f1adf81f29f6e2d5fead0e029911d7417b3d6e9221051e659f71d8953a75","2026-06-02T19:00:23.539Z","2026-06-02-add-relevance-sort-option-to-search-endpoints",{"id":88,"severity":38,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KT4DK9XQ71P90YFNQ3KQ0RD1","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.","ac9b278698d036fc25aec1c5bb4be8d48f9523d9c22bb9686210ae5099b52c2a","2026-06-02T15:00:26.167Z","2026-06-02-remove-team-field-from-duplicate-project-request-body",{"id":95,"severity":46,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KSM75S9Y2QBJDMWKMM9D1JAM","Clarified portfolio filtering behavior for service accounts","Documentation for the `GET \u002Fportfolios` 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.","4c165ce03a487557d86530e8dd6df47c62a929672f369991486e66c936e76dc3","2026-05-27T08:00:20.798Z","2026-05-27-clarified-portfolio-filtering-behavior-for-service-accounts",{"id":102,"severity":25,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KS5V44S1NY6Y91EGD3CBNQ2D","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.","b3dcd9ce0bf2e67f7649ae02ecc4ffcf279f99b1e7150126b475d5ece0721407","2026-05-21T18:00:22.049Z","2026-05-21-add-reference-custom-field-type-and-enum-constraints",{"id":109,"severity":46,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KS3XAGDG2KS2ZRP8V1N60SGY","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 \u002Fagents` endpoint. These are documentation and schema configuration changes that do not affect the actual API behavior or client integration.","a8418eaad280cf0c2088574cb955c2cec527a871497a09ebb9ba5f32232586a6","2026-05-21T00:00:18.864Z","2026-05-21-documentation-updates-for-agents-endpoint",{"id":116,"severity":25,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KS359JK7VG6MAKWPNN2WGS4C","Add Agents API with AI Teammates support","New **Agents** resource and endpoints added to support AI Teammates. Includes two new endpoints (`GET \u002Fworkspaces\u002F{workspace_gid}\u002Fagents` and `GET \u002Fagents\u002F{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.","bcb4f889e1a261e2f54164f0e070af54c5347ac2f595044bda3f1cde365c9b87","2026-05-20T17:00:22.503Z","2026-05-20-add-agents-api-with-ai-teammates-support"]