Forge to APS Migration Guide
Complete migration guide from Forge Platform to Autodesk Platform Services (APS). Updated endpoints, authentication changes, and automation tools.
Migration Overview
Why Migrate?
- • Forge API deprecation timeline: Legacy endpoints sunset December 2024
- • Improved performance and reliability with APS
- • New features and enhanced security
- • Future-proof your applications
Breaking Changes
- • Base URL change:
developer.api.autodesk.com→developer.api.autodesk.com - • Some endpoint paths have changed
- • OAuth flow improvements (backward compatible)
- • Response format changes for certain APIs
Endpoint Mapping
Authentication
| Forge (Old) | APS (New) |
|---|---|
| POST /authentication/v1/authenticate | POST /authentication/v2/token |
| POST /authentication/v1/refreshtoken | POST /authentication/v2/token |
Data Management
| Forge (Old) | APS (New) | Status |
|---|---|---|
| GET /oss/v2/buckets | GET /oss/v2/buckets | Same |
| POST /oss/v2/buckets | POST /oss/v2/buckets | Same |
| PUT /oss/v2/buckets/{bucket}/objects/{object} | PUT /oss/v2/buckets/{bucket}/objects/{object} | Same |
Model Derivative
| Forge (Old) | APS (New) | Status |
|---|---|---|
| POST /modelderivative/v2/designdata/job | POST /modelderivative/v2/designdata/job | Same |
| GET /modelderivative/v2/designdata/{urn}/manifest | GET /modelderivative/v2/designdata/{urn}/manifest | Same |
Migration Steps
Step 1: Update Base URLs
The primary change is ensuring you're using the correct base URL. Most endpoints remain the same.
Before (Forge):
const BASE_URL = 'https://developer.api.autodesk.com';After (APS):
const BASE_URL = 'https://developer.api.autodesk.com';✅ Good news: The base URL is the same! Most of your code won't need changes.
Step 2: Update Authentication
OAuth flows are backward compatible, but you should update to the v2 endpoints for better performance.
RAPS Migration (Recommended):
# Install RAPS for automatic APS compatibility
cargo install raps
# Test your existing credentials
raps auth test
# If you have Forge credentials, they work with APS
raps auth loginStep 3: Test Your Application
Most Forge applications work unchanged with APS. Test core workflows to ensure compatibility.
Testing Checklist:
# Test authentication
raps auth test
# Test file upload
raps upload test-file.dwg
# Test translation
raps translate test-file.dwg
# Test viewing
raps view test-file.dwgStep 4: Update Error Handling
Error codes and messages remain largely the same. Review our error codes reference for any changes.
# Check for any new error patterns
raps --verbose your-command
# See comprehensive error reference
# Visit: /resources/error-codesAutomated Migration with RAPS
Zero-Downtime Migration
RAPS handles the migration automatically. Your existing Forge credentials and workflows work immediately with APS.
What RAPS Handles:
- ✅ Automatic endpoint routing
- ✅ Token compatibility
- ✅ Error code translation
- ✅ Rate limit handling
- ✅ Region management
What You Need to Do:
- 📦 Install RAPS
- 🔑 Import existing credentials
- 🧪 Test your workflows
- 🚀 Deploy with confidence
Quick Start:
# Install RAPS
cargo install raps
# Import your existing Forge app credentials
raps auth login
# Test everything works
raps auth test
raps bucket list
raps translate --help
# You're migrated! 🎉Migration Troubleshooting
My OAuth tokens stopped working
This usually means you're hitting deprecated endpoints. Update to APS endpoints:
raps auth login --force-refreshGetting 404 errors on API calls
Check if you're using the correct base URL and endpoint paths. See the mapping table above.
raps --verbose <your-command> # Debug API callsPerformance issues after migration
APS has updated rate limits. Use RAPS built-in retry logic:
raps --retry-on-rate-limit <your-command>