Why request the information in writing?
A third-party integration request should identify the venue, the workflow and who is authorised to grant access. A documented response avoids ambiguity between support, the customer and the integrator.
Before you send
Include the outlet name, support or contract reference, intended use case, authorised technical contact and requested reply date. Do not request that credentials be emailed.
Suggested email
Subject: Oracle Simphony Cloud release, STS Gen2 subscription and third-party integration access
Hello, we are evaluating a connection between our Oracle Simphony environment and an authorised third-party technology provider for [reservation-to-check/eligible prepayment] workflows. Please confirm in writing our Simphony Enterprise, POS client and Reporting and Analytics versions, service delivery model, and current API subscription status.
Please confirm whether STS Gen2 access is enabled under our subscription, any required additional licence or fee, who can create a dedicated API account and how outlet-level permissions are configured. If there is a technical or contractual restriction, please identify the specific reason, available resolution and next steps.
We would appreciate your response by [date]. Credentials and tokens should be exchanged only through an approved secure channel. Thank you.
Classify the response
When access is ready, agree on account ownership, scope and testing. For a missing subscription, request the exact offering and cost; for a version issue, ask for current and supported releases. For a general refusal, request a specific technical or contractual explanation.
Oracle's open integration programme does not mean unrestricted, free API access for every customer. Use the readiness checklist to resolve missing details.
When the reply is incomplete
If the provider replies only that an integration is 'not supported', ask which condition prevents it: the deployed release, an STS Gen2 subscription or administrator privileges needed to provision an external account. State the exact transaction and target outlet rather than making an open-ended request.
Ask for a named owner, a technical explanation and the next actionable step. Preserve ticket numbers, dates and quoted licensing items. Do not infer a breach of contract or unlawful conduct before reviewing the venue's actual agreement.
Plan the next technical step
Rezervem is an Oracle partner with an STS Gen2 integration. Once permissions and licensing are confirmed, the venue can compare its requirements with the verified Simphony integration scope and organise a controlled test.
