Autodesk Vault API Integration & SDK Development
Custom applications, services and extensions built with the Autodesk Vault SDK. We connect Vault files, items, properties, BOMs and change orders with your web portals, business systems and engineering tools.
Vault data available to every system that needs it
The Vault SDK exposes Vault's web services through .NET: documents, folders, file versions and associations, properties, lifecycles, items, BOMs, change orders, users and security. The Vault Development Framework (VDF) simplifies common tasks such as login, file acquisition and property access, and the Explorer extension framework lets developers add new commands and tabs.
ENGIMANDI uses the Vault SDK to build integrations and custom applications: read-only web portals for production and suppliers, REST services that expose Vault data to other systems, extensions that add business logic to Vault Explorer, event handlers that validate actions, and background services that synchronise data with ERP, PLM or document management. All code follows Autodesk's supported APIs and licensing rules.
See CAD integration with Teamcenter, Windchill, ENOVIA and Vault.
What you get
- Vault SDK applications in C#
- REST services over Vault data
- Web portals for viewing files
- Explorer extensions & tabs
- Event handlers & validation
- Items, BOMs & change orders
- Background sync services
- Secure, licence-compliant design
Vault API development
Everything the Vault SDK can reach.
Files & Folders
Search, download, check in, check out and move files with correct associations.
Properties
Read and update user-defined properties and mappings with validation.
Items & BOMs
Item records, BOM structures and item-file links read or updated from other systems.
Change Orders
Change orders created, routed and reported through the API.
Events
Web service events used to check or block actions such as state changes and deletes.
Web Access
Browser portals showing released drawings and data to production and partners.
Vault API stack
SDK and integration technologies.
Typical projects
- Shop floor portal showing released PDFs by part number
- REST API for ERP to query Vault items
- Custom Vault Explorer tab showing ERP stock
- Delete protection for released files
- Change order report for quality audits
- Nightly property sync with PLM
How we build Vault integrations
Analyse
Data, users and systems involved.
Design
APIs, security and licensing.
Develop
Services, extensions and portals.
Test
Test Vault with real data.
Deploy
Installation, monitoring and support.
Vault API questions
Does a Vault integration need a licence?
API access follows Autodesk's Vault licensing. Some read-only scenarios have options, and we design integrations to stay compliant.
Can we access Vault from a web app?
Yes. A back-end service uses the Vault SDK and exposes the data your web app needs.
Can Vault actions be blocked by rules?
Yes. Web service event handlers can validate and cancel actions such as lifecycle changes.
Should we query the Vault database directly?
No. Direct database access is unsupported. We always use the Vault SDK.
Which Vault versions do you support?
Current and recent Vault versions. Integrations are tested for your version.