Trigger a ThingWorx event or execute a Thing service remotely via REST to drive machine-data workflows
domain: support.ptc.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
List available services on a Thing with GET /Things/{thingName}/serviceDefinitions to see valid service names and parameters
POST /Things/{thingName}/Services/{serviceName} with a JSON body containing the service's required parameters to execute it
Define an event and its associated DataShape ahead of time via AddPropertyDefinition/AddEventDefinition-style setup calls if one doesn't already exist
POST /Things/{thingName}/Events/{eventName} with a JSON body matching the event's registered DataShape to trigger it
Confirm downstream subscriptions fired by checking Thing state or logs in ThingWorx Composer
Known gotchas
The event body must match the pre-registered DataShape exactly — mismatched fields cause the call to fail rather than partially succeed
Entity-level bulk operations (Create/Read/Update/Delete across entity types) go through a separate EntityServices resource, not the per-Thing Services path
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?