About Beta Features
Overview
This API contains a combination of Generally Available (GA) and Beta endpoints.
Beta endpoints are clearly identified in the documentation. For this API, Beta designation applies only to endpoints — not to individual request parameters, request fields, response fields, enum values, or other sub-elements of an endpoint.
Unless an endpoint is explicitly marked Beta, treat it as generally available and subject to the standard API compatibility and lifecycle guarantees.
In the REST API Reference, Beta endpoints are marked with a Beta label. Each endpoint is either entirely Beta or entirely generally available — no fields or parameters are individually marked as Beta.
What Beta Endpoints Mean
Beta endpoints are intended for testing, evaluation, and feedback. They may not be complete and may undergo significant changes before reaching general availability.
During the Beta period, we may:
- Modify request or response formats
- Add, change, or remove functionality
- Adjust performance characteristics or service limits
- Change authentication, authorization, or usage requirements
- Deprecate or replace the endpoint entirely
Changes to Beta endpoints are not treated as breaking changes under the API compatibility guidelines.
While we will make reasonable efforts to communicate significant changes, Beta endpoints do not carry the same compatibility guarantees as generally available endpoints.
Production Use
Do not use Beta endpoints in production systems or mission-critical workflows.
If your application depends on Beta endpoints, design it to accommodate potential changes and interruptions.
Support and Service Commitments
Beta endpoints may have:
- Limited support availability
- Reduced documentation coverage
- Different service-level expectations than GA endpoints
- Incomplete monitoring, logging, or operational tooling
Unless otherwise specified, Beta endpoints are not covered by any service level agreements (SLAs) applicable to generally available services.
Beta Endpoints
The following endpoints are currently designated as Beta:
- File Upload, File, and Folder Operations:
- POST /vaults/{vaultId}/file-uploads
- PUT /vaults/{vaultId}/file-uploads/{uploadId}/parts/{partIndex}
- POST /vaults/{vaultId}/file-uploads/{uploadId}:complete
- POST /vaults/{vaultId}/files
- POST /vaults/{vaultId}/files/latest
- POST /vaults/{vaultId}/files/{id}:checkout
- POST /vaults/{vaultId}/files/{id}:undo-checkout
- POST /vaults/{vaultId}/files/{id}:update-properties
- POST /vaults/{vaultId}/files/{id}:checkin
- POST /vaults/{vaultId}/files:update-categories
- GET /vaults/{vaultId}/files/{id}/attributes
- PUT /vaults/{vaultId}/files/{id}/attributes
- POST /vaults/{vaultId}/folders
- Item Operations:
- Category, Unit of Measure, and Numbering Scheme Endpoints:
Providing Feedback
Your feedback plays an important role in the development of Beta endpoints. Report issues, share use cases, and provide suggestions through the Autodesk Feedback Community portal.
Transition to General Availability
When a Beta endpoint reaches general availability, it becomes subject to the standard API compatibility, support, and lifecycle policies.
The final GA implementation may differ from the Beta implementation based on customer feedback, operational learnings, and product requirements.