Autodesk Platform Extensions
Custom extensions on the Autodesk platform using APS and ACC APIs with webhook-driven automation to support tailored user workflows and sync platform events.
Problem
Standard Autodesk platform flows could not cover all internal approval steps and custom operations ONECAD teams needed during document and model lifecycles.
My Contributions
- Built custom extensions integrating Autodesk Platform Services (APS) and ACC APIs
- Implemented webhook handlers for platform events such as uploads, reviews, and status changes
- Designed idempotent event processing with retry-safe handlers and signature verification
- Mapped Autodesk events to internal business actions and user-facing workflow steps
- Developed extension UI hooks so power users can run custom operations without leaving the platform
- Containerized webhook handlers and API services with Docker for consistent deployment
- Set up Jenkins CI/CD pipelines for automated extension builds and releases
- Monitored webhook throughput and error rates with Grafana dashboards
AI-Augmented Delivery
- AI-assisted research on Autodesk APS/ACC documentation and webhook payload shapes
- Cursor agents scaffolded handler boilerplate; manually verified signature validation and idempotency keys
- Custom Cursor skills kept extension changes within defined API and workflow module boundaries
Key Features
- Custom Autodesk platform extensions for tailored user operations
- APS / ACC API integration for auth, metadata, and data sync
- Webhook-driven automation for document and model lifecycle events
- Event queue with idempotent handlers and retry logic
- Extension layer bridging Autodesk events to internal workflows
- Docker containerization for webhook and API services
- Jenkins CI/CD for automated extension deployment
- Grafana monitoring for webhook health and queue metrics
Technical Highlights
- → Webhook pipeline reduced manual status updates across project teams
- → Idempotent handlers prevented duplicate processing on webhook retries
- → Extension layer let users complete custom Autodesk workflows in one place
- → Grafana alerts surfaced webhook failures before they impacted downstream workflows
Challenges & Solutions
Out-of-order or duplicate webhook deliveries from Autodesk
✓ Event queue with idempotency keys, signature verification, and ordered processing per resource
Mapping heterogeneous Autodesk event payloads to unified internal actions
✓ Normalized event schema layer before dispatching to workflow services
Silent webhook handler failures in production without visibility
✓ Grafana dashboards and alerts on error rate, queue depth, and handler latency