Create a STSG2 API account in the Simphony back-office or Enterprise Back Office (EBO), setting the Client Scope to Both or Local depending on whether your integration targets cloud or on-premises deployments
Authenticate by sending credentials to the Oracle OpenID provider to receive an id_token and a refresh token; include the id_token as the Bearer token in the Authorization header for all subsequent STSG2 API calls
For on-premises deployments, ensure your connection uses TLS 1.2 or higher, as the local STSG2 API requires X.509 certificate validation at the transport layer
Retrieve the location and revenue center identifiers from the Simphony Configuration and Content API before constructing your transaction payload
POST your order or transaction payload to the STSG2 endpoint for the target location and revenue center, including required fields such as employee reference, order type, and line item details
Monitor the response for transaction status codes and handle errors such as invalid revenue center references or authentication token expiry with appropriate retry or re-authentication logic
Known gotchas
Cloud and on-premises Simphony deployments use different authentication flows; the cloud uses Oracle OIDC directly while on-premises uses EBO IDM tokens — mixing them will result in authorization failures
The id_token has a limited lifetime; build token refresh into your integration before the token expires to avoid failed transaction submissions during busy service periods
Revenue center and location identifiers must match exactly what is configured in Simphony; a mismatch causes transaction rejection even if authentication succeeds
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