Which Asana API endpoints were removed recently?

None between 28 April 2026 and 29 October 2026, in defs/asana_oas.yaml in Asana/openapi. It went from 245 to 271 operations in that window, and every operation present at the start was still there at the end, at the same URL.

Did any Asana API request fields become required?

1 JSON request field became required between 28 April 2026 and 29 October 2026: data.color on POST /projects/{project_gid}/project_statuses. It is nested, so it applies only inside each object containing it (the part before the last dot; for an array, each element) that a JSON request body sends: such an object sent without the field no longer matches the current specification, and a body that omits the object, or sends an empty array, is unaffected.

Where is the Asana OpenAPI specification?

In the Asana/openapi repository on GitHub. This page reads defs/asana_oas.yaml at commit 81d7701 (version 1.0), dated 29 October 2026.

What Asana changed, 28 April 2026 to 29 October 2026

245 operations became 271. None were removed, 0 were newly deprecated, 26 were added, and 1 request field became required.

Read from Asana/openapi at e698f9a and 81d7701 (version 1.0). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Asana's published specification.

Asana publishes its API description in Asana/openapi. This page reads defs/asana_oas.yaml, not the SDK or app-components files beside it. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.

Removed from the specification

Nothing was removed in this window. That is a real result, not a gap in the check.

Newly deprecated in this window

A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.

No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.

1 operation in the deprecated list below has no matching operation at the baseline, so it is not classified here: the snapshot does not show whether it arrived deprecated or gained the flag later.

Deprecated as of the current specification (1)

Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.

GET /tables/{table_gid}/getCustomFieldSettings

Request fields removed from the specification

The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Asana rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Asana versions — see the note at the top of this page.

POST /projects/{project_gid}/duplicate no longer lists data.team (application/json)

Request fields that became required

Only JSON request bodies are compared. A top-level field applies whenever the operation is sent a JSON body. A nested field applies only inside each object containing it that is sent (for an array, each element), so a caller that never sends that object, or sends an empty array, is not affected.

POST /projects/{project_gid}/project_statuses — now requires data.color when data is sent

Asana API questions

Every answer below is computed from the snapshot above, and each links to the Asana specification it was read from.

Which Asana API endpoints were removed recently?: None between 28 April 2026 and 29 October 2026, in defs/asana_oas.yaml in Asana/openapi. It went from 245 to 271 operations in that window, and every operation present at the start was still there at the end, at the same URL.; Source: Asana/openapi, the two commits compared
Which Asana API endpoints are deprecated?: As of 29 October 2026, defs/asana_oas.yaml in Asana/openapi marks 1 operation deprecated: GET /tables/{table_gid}/getCustomFieldSettings. No compared operation (one the comparison paired with a baseline operation) gained the deprecated flag between 28 April 2026 and 29 October 2026. 1 has no matching operation at the baseline (added during the window), so this page does not say whether it arrived deprecated or was deprecated later.; Source: Asana/openapi, the two commits compared
Did any Asana API request fields become required?: 1 JSON request field became required between 28 April 2026 and 29 October 2026: data.color on POST /projects/{project_gid}/project_statuses. It is nested, so it applies only inside each object containing it (the part before the last dot; for an array, each element) that a JSON request body sends: such an object sent without the field no longer matches the current specification, and a body that omits the object, or sends an empty array, is unaffected.; Source: Asana/openapi, the two commits compared
Where is the Asana OpenAPI specification?: In the Asana/openapi repository on GitHub. This page reads defs/asana_oas.yaml at commit 81d7701 (version 1.0), dated 29 October 2026.; Source: Asana/openapi on GitHub

The Action does not check Asana yet

It checks GitHub REST and Stripe. If you want your CI to check the Asana endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.

a real report