API CHANGE

Autodesk Platform Services API 2.0: Breaking Changes Incoming

By Marcin K. February 15, 2026 8 min read

CRITICAL IMPACT

This update requires immediate attention and may affect your current operations.

🔑 Key Finding

All v1 endpoints shut down June 1, 2026. No grace period. Your integrations WILL break without migration.

✅ Action Item

Audit all Autodesk API calls TODAY. Budget 40-60 hours for typical integration. Start sandbox testing by March 1 to avoid June breakage.

Autodesk announced Platform Services API 2.0 will deprecate v1 endpoints on June 1, 2026—four months from today. All integrations currently using v1 authentication, data access, or webhooks will stop working on that date. No grace period. No fallback compatibility mode. Clean cutoff.

For firms with custom integrations between BIM 360, Construction Cloud, or Autodesk products and internal systems (ERP, project management, business intelligence), this is a CRITICAL event requiring immediate action.

What’s Changing: The Technical Details

Platform Services (formerly Forge API) is Autodesk’s developer platform for programmatically accessing BIM 360, Construction Cloud, Revit Cloud Worksharing, and other Autodesk services. Common use cases:

Extract project data (drawings, models, RFIs, submittals) into business intelligence dashboards
Sync with ERP systems (push budget/cost data from Procore/Sage to Autodesk)
Automate workflows (create projects, assign permissions, generate reports programmatically)
Custom integrations (connect Autodesk to proprietary internal systems)

API 2.0 Breaking Changes:

1. Authentication: OAuth 2.0 Required

v1 (Deprecated):

POST /authentication/v1/authenticate
{
  "client_id": "your_app_id",
  "client_secret": "your_secret",
  "grant_type": "client_credentials"
}

v2 (Required after June 1):

POST /authentication/v2/token
{
  "client_id": "your_app_id",
  "client_secret": "your_secret",
  "grant_type": "client_credentials",
  "scope": "data:read data:write"
}

The change: Explicit scopes required. v1 granted all permissions by default. v2 requires declaring exactly which data you’re accessing. This improves security but breaks existing code.

Migration effort: 10-15 hours to update authentication across all integrations, test scope permissions, handle token refresh logic.

2. Endpoint Structure Changes

v1:

GET /project/v1/hubs/{hub_id}/projects/{project_id}/items

v2:

GET /data/v2/projects/{project_id}/folders/{folder_id}/contents

The change: URL structure redesigned. Projects now use unified /data/v2/ namespace instead of scattered endpoints. Folder hierarchy is more explicit.

Migration effort: 15-25 hours to update all API calls, remap folder/file paths, test data retrieval.

3. Rate Limits Reduced

v1 Rate Limits:

Free tier: 10,000 requests/day
Paid tier: 100,000 requests/day

v2 Rate Limits:

Free tier: 5,000 requests/day
Paid tier: 50,000 requests/day (unless you purchase additional capacity)

The change: 50% reduction in allowed requests. Integrations that poll frequently or process large batches may hit limits.

Migration effort: 10-20 hours to implement caching, reduce unnecessary API calls, optimize batch processing, or purchase higher limits.

4. Webhook Payload Format Changes

v1 Webhook:

json

{
  "hook": {
    "hookId": "abc123",
    "event": "dm.version.added"
  },
  "payload": {
    "version": "urn:adsk.wipprod:dm.lineage:abc123"
  }
}

v2 Webhook:

json

{
  "eventId": "evt_xyz789",
  "eventType": "data.version.created",
  "resource": {
    "urn": "urn:adsk.wipprod:fs.file:vf.abc123?version=2",
    "projectId": "proj_123"
  },
  "timestamp": "2026-02-12T10:30:00Z"
}

The change: Payload structure completely redesigned. Field names changed, nesting structure altered, timestamps added.

Migration effort: 15-30 hours to update webhook handlers, remap field names, test all event types.

Total Migration Effort: 40-80 Hours

For a typical integration (authentication + data extraction + webhook handling), expect:

Small integration: 40-50 hours
Medium integration: 50-70 hours
Complex integration: 70-100+ hours

At $150/hour blended developer rate, this is $6,000-15,000 per integration in labor costs.

Timeline & Deadlines

February 12, 2026 (Today):

Announcement published
v2 API available in production
v1 still functional

March 1, 2026:

v1 deprecation warnings appear in API responses
Autodesk Developer Portal displays migration guides

April 1, 2026:

v1 rate limits reduced to 50% (force migration pressure)
v2 becomes default in documentation

May 1, 2026:

v1 deprecation warnings become errors (warnings in responses, not failures)
Final migration deadline reminders sent

June 1, 2026:

v1 endpoints SHUT DOWN
All unmigrated integrations STOP WORKING
No grace period, no compatibility mode

Timeline from today to shutdown: 109 days (15.5 weeks)

For firms with complex integrations, this is tight. Budget 6-8 weeks for migration, 4 weeks for testing, 2-4 weeks for deployment and monitoring.

Impact Analysis: Who’s Affected

Definitely Affected:

Custom integrations between Autodesk and ERP systems (Sage, Foundation, SAP)
Business intelligence dashboards pulling Autodesk data (Power BI, Tableau)
Workflow automation tools (Zapier, Make, custom scripts)
Data synchronization between Autodesk and other platforms (Procore, PlanGrid sync)
Internal portals displaying project data from BIM 360/ACC

Possibly Affected:

Third-party apps in Autodesk App Store (if they use Platform Services API)
Plugins for Revit/AutoCAD that access cloud data
Mobile apps built on Platform Services

Not Affected:

Users who only use Autodesk web/desktop apps (no custom code)
Integrations built on partner APIs (Procore <> Autodesk direct integration)
Autodesk-built features (Construction IQ, BIM Collaborate)

How to Identify Your Risk

Step 1: Inventory Integrations

Search your codebase for:

authentication/v1
project/v1
dm.version (old webhook event names)
forge.autodesk.com/api (old API domain)

If found → You’re affected.

Step 2: Check Third-Party Tools

Ask vendors:

“Does your integration use Autodesk Platform Services API?”
“Have you migrated to v2?”
“What’s your timeline for v2 support?”

If vendor says “we’re working on it” → You’re at risk.

Step 3: Test in Sandbox

Create test project in Autodesk Developer Portal, use v2 endpoints, verify your integration works.

If errors occur → Plan migration immediately.

Migration Resources

Autodesk provides:

1. Migration Guide

URL: https://aps.autodesk.com/migration-guide
Content: Side-by-side comparison of v1 vs v2 endpoints
Quality: Comprehensive but technical (requires developer expertise)

2. Code Samples

GitHub: github.com/autodesk-platform-services/aps-tutorials
Languages: JavaScript, Python, C#, Java
Quality: Basic examples, not production-ready

3. Sandbox Environment

Free test environment with v2 API access
Use for development/testing before production deployment

4. Developer Support

Forum: https://aps.autodesk.com/forums
Response time: 24-48 hours (community support, not guaranteed)
Paid support: Available via Autodesk customer success (expensive)

Cost Breakdown: Migration Budget

Typical Firm (3 integrations):

Integration	Hours	Cost @ $150/hr
ERP sync (Sage → Autodesk)	60 hours	$9,000
BI Dashboard (Power BI)	40 hours	$6,000
Automation scripts (Python)	30 hours	$4,500
Total	130 hours	$19,500

Alternative: Hire Consultant

Autodesk partner consultants charge:

Rate: $200-300/hour
Typical engagement: $25K-40K for 3 integrations
Benefit: Expertise, faster delivery
Risk: Dependent on consultant availability

Why This Matters: Real Scenarios

Scenario 1: ERP Integration Breaks

Your custom integration syncs project budgets from BIM 360 to Sage Accounting every night. On June 1, integration stops working. Consequences:

Budget data in Sage becomes stale
Project managers make decisions on outdated financials
Month-end close delayed by 5-7 days
Financial reporting to executives compromised

Recovery time: 2-4 weeks to diagnose, migrate, and redeploy.

Scenario 2: Dashboard Goes Dark

Your executive dashboard pulls live data from Construction Cloud showing project status across 50 active projects. On June 1, dashboard shows errors. Consequences:

Executives lose real-time visibility
Weekly leadership meetings disrupted
Data team scrambles to migrate integration
Trust in digital tools eroded

Recovery time: 1-3 weeks.

Scenario 3: Workflow Automation Fails

You’ve automated project creation: When ERP creates new job number, script auto-creates BIM 360 project with correct folder structure and permissions. On June 1, automation stops. Consequences:

Project teams manually create BIM 360 projects (30-45 min each)
Inconsistent folder structures
Permission errors causing access delays
10-15 hours/week wasted on manual work

Recovery time: 2-3 weeks.

The Common Thread

All scenarios involve workflow disruption, data delays, and emergency scrambling. The cost isn’t just migration labor ($20K)—it’s operational chaos ($50K+ in lost productivity, delayed decisions, and firefighting).

Autodesk’s Motivation: Why Force Migration?

Security:

v2 has better OAuth 2.0 implementation (scoped permissions, token rotation)
v1 had overly broad permissions (security risk)

Scalability:

v2 API infrastructure is more efficient
v1 backend is expensive to maintain
Shutting down v1 reduces Autodesk’s infrastructure costs

Developer Experience:

v2 has cleaner, more consistent design
Easier to build new features on v2 architecture

Commercial:

v2 rate limits push customers to paid tiers
Generates additional revenue from API usage fees

Autodesk’s motivations are legitimate—v2 is objectively better. But forcing migration in 4 months is aggressive.

What Autodesk Should Have Done

Better Timeline:

Announce 12 months in advance (not 4)
Provide 6-month compatibility mode (both v1 and v2 work)
Gradual deprecation (warnings → errors → shutdown over 18 months)

Better Migration Support:

Automated migration tools (convert v1 code to v2)
Free consulting for high-impact customers
Extended timeline for complex integrations

What They Actually Did:

4-month notice
Basic documentation
“Figure it out or break” approach

This disrespects customers who’ve invested in Autodesk integrations and creates unnecessary disruption.

What You Should Do Now

Week 1 (This Week):

Inventory all Autodesk API integrations
Identify affected systems
Estimate migration effort (use 50-70 hours as baseline)
Communicate to leadership/stakeholders

Week 2-3: 5. Assign developer resources (internal or consultant) 6. Create migration project plan 7. Set up v2 sandbox environment 8. Begin authentication migration

Week 4-8: 9. Migrate endpoint calls 10. Update webhook handlers 11. Optimize for new rate limits 12. Test in sandbox thoroughly

Week 9-12: 13. Deploy to production (staged rollout) 14. Monitor for errors 15. Fix issues as they arise 16. Document new integration for future maintenance

Week 13-15: 17. Final testing 18. Decommission v1 code 19. Celebrate avoiding June 1 disaster

If You Don’t Migrate:

June 1, 2026:

Your integrations stop working
Emergency developer allocation (costly)
2-4 week scramble to fix
Operational chaos
Angry executives/stakeholders

Bottom Line: This Is CRITICAL

Autodesk’s Platform Services API 2.0 migration is not optional. It’s not a suggestion. On June 1, 2026, v1 endpoints shut down permanently.

If you have custom integrations with Autodesk products, this is a CRITICAL priority. Budget 40-80 hours of developer time, start immediately, and plan for completion by May 1 to allow buffer for issues.

The cost of migrating ($6K-20K) is far less than the cost of broken integrations on June 1 ($50K+ in operational disruption).

Action items:

Audit Autodesk API usage TODAY
Budget migration resources THIS WEEK
Start development by March 1
Complete testing by May 1
Deploy by May 15

Firms that delay past March will be scrambling in May. Firms that ignore this will face disaster June 1.

You’ve been warned.

Source: Autodesk Developer Blog