When to use: Your integration sits between Speckle and enterprise systems (PLM, data lakes, scheduling, proprietary APIs) without owning a host-application UI.
Typical stack:
Docs: Key concepts · Updating syncs · Webhooks
Design notes
- Treat versions as immutable inputs; design jobs to be replayable from a known version id.
- Separate read paths (pull from Speckle) from write paths (push new versions) so failures are easier to reason about.
- Prefer explicit mapping tables for external system ids ↔ Speckle
applicationId values.
Last modified on July 18, 2026
