The API Report CardAPI Index
PTC Creo

PTC Creo API

ptc.com

No REST API for the Creo modeler; automation runs through in-process desktop toolkits (C, C++, Java, JavaScript) inside a licensed seat. TOOLKIT entitlements require specific subscription tiers. Major releases break custom code; Windchill adds REST and OSLC on the PLM side.

Last verified: July 2026Manufacturing
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODC TOOLKIT, C++ OTK, Java J-Link, and Web.Link expose thousands of modeler functions; Windchill adds REST and OSLC.
AccessMIXEDTOOLKIT entitlements require specific Creo subscription tiers; customization support is not in every seat.
CoverageMIXEDModeling, assembly, drawing, UI, and event callbacks are reachable in-process; nothing works without a running Creo seat.
AuthMIXEDToolkit code runs under the Creo seat license with no auth model; Windchill uses session, basic, or OAuth 2.0.
Docs & DXGOODAPIWizard reference docs ship with every install, backed by an active PTC customization community forum.
StabilityMIXEDMajor releases break TOOLKIT apps; moving from Creo 7 to 11 means recompilation and code adjustments.
Supergood: PTC Creo has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

PTC Creo scores C on the API Report Card. No REST API for the Creo modeler; automation runs through in-process desktop toolkits (C, C++, Java, JavaScript) inside a licensed seat. TOOLKIT entitlements require specific subscription tiers. Major releases break custom code; Windchill adds REST and OSLC on the PLM side.

Tried to integrate with PTC Creo?
SOURCES
TOOLKIT requires a specific Creo entitlement / tier, not all subscriptions include customization support ptc.com
In-process C TOOLKIT means crashes in custom code take down the user's Creo session; no sandboxing community.ptc.com
No public REST API for the Creo modeler itself, every integration has to embed into the desktop client or go through Windchill ptc.com
API surface fragmented across TOOLKIT (C), OTK (C++/Java), J-Link, VB API, Web.Link, Creo.JS, Creo View Web Toolkit, Schematics API, Elements/Direct .NET, confusing for new developers picking a path community.ptc.com
APIWizard documentation is shipped with the product as static HTML, not on a developer portal, hard to link, search, or version externally support.ptc.com
Breaking changes between Creo major releases (e.g. 7 -> 11) require recompilation and frequent code adjustment of TOOLKIT apps community.ptc.com
Web.Link is browser-embedded inside Creo, not a way to drive Creo remotely from a separate web app support.ptc.com
No webhooks at the Creo level; only Windchill exposes event/subscription mechanisms ptc.com
Granite kernel licensing is enterprise-only and not realistic for small integrators ptc.com
OSLC adoption helps but third-party PLM linking still varies in fidelity across Teamcenter/ENOVIA ptc.com
Creo+ SaaS does not currently expose a public REST API for the modeler; cloud-era developer story remains immature compared to Onshape community.ptc.com
Community/forum responses to TOOLKIT questions are uneven; specialist consultants (PLM Coach, LearnCAx, 3HTi) often required plmcoach.com
Steep learning curve and dated UI ribbon; new engineers coming from SOLIDWORKS find Creo unforgiving g2.com
Crashes and instability on very large assemblies; stability regressions across point releases peerspot.com
Expensive vs SOLIDWORKS and Solid Edge, Essentials/Advanced/Premium tiers plus per-module surcharges add up quickly itqlick.com
Subscription pricing pressure post-2019 perpetual sunset; customers report aggressive maintenance increases trustradius.com
File migration pain across major versions (Creo 7 -> 8 -> 9 -> 10 -> 11); regenerate failures on legacy parts community.ptc.com
2D drafting workflow feels slow and dated vs AutoCAD/SOLIDWORKS DraftSight capterra.com
Autosave and crash recovery are weak, users repeatedly cite lost work g2.com
Multi-CAD round-tripping via Creo Unite has fidelity issues with native SOLIDWORKS/NX/CATIA models community.ptc.com
STEP/IGES export sometimes downgrades solid to surface geometry; Creo 9+ improvements for AP242 PMI community.ptc.com
Windchill integration is powerful but heavyweight; small teams find it overkill, large teams find the admin burden significant gartner.com
Creo+ (SaaS) early-adopter friction: limited feature parity with desktop Creo, license-server hybrid is confusing community.ptc.com
Linux support increasingly minimal; Windows-only in practice support.ptc.com