22 Jul 2026

Forma Takeoff API Classification and Sheet Reference Migration/Deprecation Announcement

Forma Takeoff API Classification and Sheet Reference Migration/Deprecation Announcement

Safe Harbor Statement:

The features and timelines described below are forward-looking and subject to change. This notice is provided for planning purposes only and is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Do not rely on this information when making purchasing decisions.


Autodesk continues to evolve the Preconstruction platform and its APIs. As part of this work, Takeoff is transitioning classification management to the Forma Classifications Service and updating how classification and sheet reference data are exposed through the Takeoff API.

Autodesk will begin migrating projects soon. As each project is migrated, its existing Takeoff classification systems will be recreated in the Forma Classifications Service, and the Takeoff project will automatically reference the new classification data.


What's Changing

The migration introduces the following high-level changes:

  • Takeoff-specific Classification Systems endpoints are being deprecated in favor of the Classifications API.
  • Takeoff API responses are being updated to reference classifications managed by the Forma Classifications Service.
  • New APIs are available for managing classification structures assigned to Takeoff projects.
  • 2D sheet references within the Takeoff API are moving from Sheets identifiers to Data Management file version URNs.

For complete technical details, including endpoint changes, payload updates, request/response examples, and migration guidance, refer to the Takeoff API Migration Guide.

 


Timeline

Date Milestone
July 22, 2026
  • Updated Takeoff API and Forma Classifications API are released.
  • Updated Takeoff API documentation and Migration Guide are published.
  • The deprecation process begins for the legacy classification endpoints and fields. They are now deprecated and will be removed after Jan 29, 2027.
Sep 1, 2026
  • Project-by-project migration begins.
Jan 29, 2027
  • All projects should be migrated.
  • Legacy classification fields (classificationCodeOne / classificationCodeTwo) and deprecated classification functionality are removed.

Project Migration

Migration is performed on a per-project basis.

During the rollout period, some projects may already use the new behavior while others continue using the legacy format. Integrations should support both formats until all of their projects have been migrated.

Detailed migration behavior is documented in the Takeoff API Migration Guide.


What You Should Do

If your application integrates with the Takeoff API, you should:

  • Review the Takeoff API Migration Guide for the complete list of API and payload changes.
  • Request a test project by emailing takeoff.migration.support@autodesk.com so you can validate your integration before the production migration.
  • Update your integration to support both legacy and migrated projects during the rollout period.
  • Complete your migration before January 29, 2027, when the deprecated functionality will be removed.

For details, please refer Takeoff API Migration Guide.


Who Is Affected?

You will need to update your integration if it uses any of the following:

  • Classification Systems endpoints
  • Classification data returned by the Takeoff API
  • classificationCodeOne or classificationCodeTwo
  • contentView.version for 2D takeoff items

If your integration does not use these capabilities, no action is required.

See the Takeoff API Migration Guide for the complete list of affected APIs and required migration steps.


Support

If you have questions about the migration or would like access to a test environment, please email takeoff.migration.support@autodesk.com to get direct support. Our team is happy to help you plan and validate your migration.

 

Related Article