OmniScripts are primarily UI components, but their underlying Integration Procedure logic can be invoked directly via REST for server-side execution.
To invoke an Integration Procedure (the server-side equivalent) via REST, POST to /services/apexrest/vlocity_cmt/v1/integrationprocedures/actions/{IPType}/{IPSubType} (the exact path may vary by OmniStudio version and namespace — verify against your org's namespace, which may be 'omnistudio' or 'vlocity_cmt').
The request body is a JSON object with an 'input' key containing the input parameters the Integration Procedure expects.
Authenticate using a standard Salesforce OAuth token; OmniStudio respects Salesforce session permissions.
The response contains an 'output' object with the Integration Procedure's return data.
For debugging, enable OmniStudio debug logging (available in the OmniStudio settings) to trace procedure execution step-by-step.
Known gotchas
The REST endpoint namespace prefix ('vlocity_cmt' vs 'omnistudio') depends on whether your org uses the managed package or the native OmniStudio version; always verify the namespace in your org before constructing the URL.
The Integration Procedure name is a combination of Type and SubType separated by an underscore in the URL path; incorrect naming returns a 404 or generic error.
OmniScripts themselves are not directly invokable via REST — only Integration Procedures are; if you need to drive an OmniScript flow programmatically, invoke the underlying Integration Procedures instead.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp