Inject a transaction into Oracle Simphony via the Transaction Services Generation 2 (STSG2) REST API and authenticate using OpenID Connect

Steps

1. 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
2. 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
3. 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
4. Retrieve the location and revenue center identifiers from the Simphony Configuration and Content API before constructing your transaction payload
5. 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
6. 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