Documented API
A versioned protocol and JSON schemas describe how to send per-part STEP geometry, assembly structure and supported updates.
CAD Bridge API
Your CAD workflow. Your connector.
Build an integration for your tools using a documented API, implementation plans and conformance tools, with help from an AI coding assistant.
The building blocks
A clear contract for your integration.
VIZid Next includes the receiving side. Your connector supplies the CAD data.
Implementation plans
CAD-specific plans help your developer or AI coding assistant build against your installed CAD system and SDK.
Conformance tools
Test a connector against the protocol before checking it with VIZid Next and representative CAD models.
How it works
Build. Check. Send.
The connector determines how and when updates are sent.
- Choose the plan for your CAD system and check its version, licence and SDK requirements.
- Work with an AI coding assistant or developer to build your connector on your machine.
- Run the conformance tools, then test the connector with your CAD installation and VIZid Next.
- Send the model and supported updates into your product scene.
Build plans cover Creo, SOLIDWORKS, Solid Edge, CATIA V5, Inventor, Fusion, NX, Rhino, FreeCAD and Onshape. These are implementation plans, not a list of supplied or certified connectors. Availability of CAD APIs and export functions depends on your vendor, version and licence.
Supported data
Send changes with intent.
The API supports geometry replacement, placement updates and hiding or restoring parts. Material rules are reapplied by name and path when geometry is replaced; stable part identity matters.
The receiving API runs on the same machine as your connector. Return messages describe data previously received; they do not send your VIZid scene edits back into CAD. A conformance result checks the protocol, not every CAD workflow.