Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

3 Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

Introduction

This chapter discusses the activation of Nor1 eStandby Upgrade and Nor1 eXpress Upgrade such as: gathering pricing information, setting go-live dates, transitioning to Nor1 Revenue Support and the OPERA Xchange Interface (OXI).

Parent topic: Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

Nor1 eStandby Upgrade Process

Once the Implementation Manager (IM) is assigned to the implementation at a property, the IM sends an introductory email to start gathering the necessary information.

The email includes a link for online data completion and implementation process detailed instructions. See the following email example:

From: (IM Name)

Sent: (Date/Time)

To: (Recipient Name)

Subject: The Revenue Hotel - Let's get your property LIVE on eStandby!

Importance: High

Dear (Property Name) team,

I am very happy to begin working with you to implement your property on Nor1 eStandby Upgrade. To see and complete the initial steps to take your property live on the solution, please complete the attached Basic Data Form or provide Accelerator details.

Please reach out to me with any questions and complete the information by (Date).

I’m looking forward to hearing from you,

(IM signature)

Parent topic: Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

IM Property Implementation Call

After the required information is completed, the Implementation Specialist works to schedule a pricing/testing call with the hotel to explain the eStandby Upgrade product and finalize the offer set and price points. As part of the call, the Implementation Manager secures a go-live date convenient to the customer. Once setup and testing are complete and the hotel is ready to go live, the IM will send a handoff email with the required training links. The handoff is sent to Nor1-art-team_us@oracle.com.

Parent topic: Nor1 eStandby Upgrade Process

Property Activation

Property activation must be discussed with the hotel as part of the Implementation call. Once all the implementation steps are completed and the property has approved going live with the program, the Nor1 Implementation Manager sends the hotel a notification email to the implementation main contact.

Parent topic: Nor1 eStandby Upgrade Process

Property Transition to Account Support

After Nor1 eStandby Upgrade is implemented, the property is transitioned to the Account Support Team.

Parent topic: Nor1 eStandby Upgrade Process

Nor1 eXpress Upgrade Process

Parent topic: Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

How It Works

To use Nor1 eXpress Upgrade with the OPERA Xchange Interface (OXI), OXI must already be configured with Nor1.

You must determine a time window for switching offers from Nor1 eStandby Upgrade to confirmed in Nor1 eXpress Upgrade.
For bookings arriving within the pre-determined number of hours, a Nor1 eXpress Upgrade offer email is sent to the guest. Guests will not receive both a Nor1 eStandby Upgrade and Nor1 eXpress Upgrade email if the guest has already made an eStandby request.
Bookings made inside the cutoff time will receive confirmed Nor1 eXpress Upgrade offers.
The guest selects a room upgrade offer and confirms selection.
OPERA PMS is updated with a fixed charge and the new room.

Parent topic: Nor1 eXpress Upgrade Process

What’s Needed from the Hotel

To successfully implement the solution, the Nor1 Implementation Specialist needs to discuss and secure the following information from the hotel:

Pricing Structure: You must discuss the pricing structure and get the hotel’s approval of the offer set.
Email Offers: Offers are typically sent 48 or 72 hours prior the day of arrival. This will be discussed and approved by the hotel subject to each property and chain.
Transaction Code: A unique OPERA transaction code needs to be secured from the hotel. This is crucial for the process since automatic posting is done through the OXI interface.

Note:
Nor1 eXpress Upgrades support room, packages, and add-on upgrades. Activation, adjustment, and support of eXpress Upgrades can be managed by Oracle Hospitality Support or your Nor1 Revenue Support team.

The following is an Implementation Specialist Email communication example:

Dear (Name),

I’m very excited to assist with your Nor1 eXpress Upgrade implementation. Please see the following summary of necessary steps to go live with the solution, as well as some important notes to read at the end of this email.

Pricing Review: Attached you will find the pricing structure we currently have in place for eStandby as a reference, and then beside it starting in column G, you will find the pricing structure for Nor1 eXpress upgrades. The intention is to choose the pricing ranges you want to display (columns I and J), please feel free to modify if needed.

Pricing can remain the same as Nor1 eStandby Upgrade. They do not have to be different between products.

Room Categories and Codes: Please advise should we be missing any room codes that you have in the OPERA PMS. We will mirror your PMS system based on codes to make sure we provide you with maximum exposure. Again, we will only offer available rooms.

Important notes:

eXpress Upgrade can present room upgrades and non-room add-ons along with packages. Non-room upgrades must be items that can be honored at any time.
We recommend emails be sent in a period of 72 hours prior to the day of arrival.
You need to create a unique transaction code for the room upgrade and each non-room add-on.
Your special constraints for pricing or blackout dates will reflect accordingly.

I am looking forward to hearing from you,

Thank you for your partnership!

Parent topic: Nor1 eXpress Upgrade Process

Nor1 eXpress API Implementation Guide

Parent topic: Nor1 eStandby Upgrade and Nor1 eXpress Upgrade

Scope

This guide provides information on the retrieval and fulfillment of eXpress API Upgrade Application Programming Interface (API) offers exposed through the Oracle Hospitality Integration Platform (OHIP). It does not cover eStandby, Check-in Merchandising UI behavior, retargeting email delivery, or the administration of legacy eXpress API rules.

Parent topic: Nor1 eXpress API Implementation Guide

Purpose

Use this guide to onboard an OHIP customer or partner integration that presents Oracle Hospitality Nor1 eXpress Upgrade Application Programming Interface (API) offers to guests and submits their selected offers. This guide is intended for external implementation teams and assumes access to the Oracle Hospitality Developer Portal and the applicable OHIP environment.

Parent topic: Nor1 eXpress API Implementation Guide

Audience

Customer and partner developers
integrating eXpress API Upgrade Application Programming Interface (API) offers into booking, mobile, kiosk, messaging, CRS/PMS, or other guest-facing applications.
Oracle Hospitality and Nor1 implementation teams validating property configuration, identifiers, and certification evidence.
Support teams troubleshooting authentication, no-offer, and offer fulfillment issues.

Parent topic: Nor1 eXpress API Implementation Guide

Prerequisites

Table 3-1 Prerequisites

Area	Prerequisites for Development
OHIP access	Developer Portal application, API plan subscription, gateway URL, client ID, client secret, OAuth scope, and x-app-key for the target environment.
Hotel details	Production or non-production environment, region, tenant or chain code, hotel ID, and any required SSD or enterprise identifier.
Nor1 setup	Hotel enabled in Nor1 Control Panel for the approved eXpress API room upgrade and/or non-room offer flow.
Identifiers	Property/hotel ID, enterprise ID or SSD context, providerId when assigned, and any Oracle/Nor1-confirmed property mapping.
Test data	Eligible reservations, ineligible/no-offer reservations, and at least one reservation suitable for successful fulfillment testing.
Commercial readiness	The sales process is complete, and the customer has the required Nor1 subscription.
Exposure timing	The third-party API exposure date aligns with the Nor1 eXpress exposure window, such as 72, 48, or 24 hours before arrival, and written confirmation is provided.
OHIP credential association	The partner must associate OAuth token credentials with the Oracle Hospitality Integration Platform (OHIP) connection used by Nor1. Refer to the Authenticating to Oracle Hospitality Property APIs guide and, where applicable, the Oracle Hospitality Property APIs with Client Credentials Authentication (OCIM) guide.
OCIM and certificate readiness	Oracle/Nor1 implementation teams must confirm whether the hotel uses Oracle Cloud Identity Management (OCIM) and whether the required public key or certificate configuration is complete for the target environment.

Parent topic: Nor1 eXpress API Implementation Guide

References

Table 3-2 References

Reference	Use
OHIP Implementation Guides	Use as the published Oracle guide index for OHIP implementation patterns. See OHIP Implementation Guides for more details.
Oracle Hospitality Nor1 Integrated Upsell APIs	Use as the OHIP parent topic for Nor1 upsell authentication and related topics. See Oracle Hospitality Nor1 Integrated Upsell APIs for more details.
Authenticating to Oracle Hospitality Property APIs	Use for OAuth, Developer Portal credentials, integration user, application key, token renewal guidance, and OCIM authentication setup. See Authenticating to Oracle Hospitality Property APIsfor more details.
Calling Oracle Hospitality Property APIs	Use for OHIP gateway header conventions, including Authorization, x-app-key, x-hotelid, and request ID guidance.
OHIP Limits	Use for header-size, body-size, OAuth token renewal, and platform throttling expectations.
Oracle Hospitality Property APIs with Client Credentials Authentication (OCIM)	Use for OCIM client credentials authentication, OAuth token credential association, and public key or certificate setup expectations where applicable. See Oracle Hospitality Property APIs with Client Credentials Authentication (OCIM) for more details.
Using the Oracle Hospitality APIs	Use as the general Oracle Hospitality API calling guide for gateway URL setup, authentication, and API request flow. See Using the Oracle Hospitality APIs for more details.
Oracle Hospitality Property APIs with Resource Owner Group Authentication (SSD)	Use as background for SSD/resource-owner authentication contexts and Oracle/OHIP onboarding configuration when applicable. See Oracle Hospitality Property APIs with Resource Owner Group Authentication (SSD) for more details.

Parent topic: Nor1 eXpress API Implementation Guide

End-to-End Flow

Confirm that the hotel, environment, enterprise or SSD context, providerId, and Nor1 eXpress API offer configuration are ready.
Obtain an OAuth access token for the target OHIP environment.
Call GET upsellOffers for the guest reservation and arrival date.
If the response is 200, present eligible offer groups to the guest. If the response is 204, treat the reservation as having no eligible offers.
When the guest selects an offer, call POST upsellOffers with the returned offerId.
Confirm the selected offer response and complete any integration-specific guest confirmation, receipt, or downstream handling.

Parent topic: Nor1 eXpress API Implementation Guide

Base URL and Resource Paths

Use the OHIP gateway URL assigned for the environment as the base URL. Append one of the resource paths below.

Table 3-3 Base URL and Resource Paths

Operation	Method	Path
Retrieve eXpress API upsell offers	GET	/ohcgep/v0/hotels/{hotelId}/reservations/{reservationId}/arrivalDate/{arrivalDate}/upsellOffers
Fulfill or select an offer	POST	/ohcgep/v0/hotels/{hotelId}/reservations/{reservationId}/arrivalDate/{arrivalDate}/upsellOffers
Retrieve offers with enterprise ID in path	GET	/{enterpriseId}/ohcgep/v0/hotels/{hotelId}/reservations/{reservationId}/arrivalDate/{arrivalDate}/upsellOffers
Fulfill offer with enterprise ID in path	POST	/{enterpriseId}/ohcgep/v0/hotels/{hotelId}/reservations/{reservationId}/arrivalDate/{arrivalDate}/upsellOffers

Parent topic: Nor1 eXpress API Implementation Guide

Path Parameters

Table 3-4 Path Parameters

Parameter	Required	Validation	Description
enterpriseId	Conditional	Present in enterprise path variant.	Enterprise identifier for OCIM-style authentication. When used in the path, separate SSD identity-provider context is not required by the eXpress API service.
hotelId	Yes	2-50 characters; letters, numbers, underscore.	OPERA hotel/property ID for the reservation.
reservationID	Yes	2-50 digits.	OPERA reservation ID.
Fulfill offer with enterprise ID in path	Yes	YYYY-MM-DD.	Arrival date for the reservation. Must match the reservation arrival date.

Parent topic: Nor1 eXpress API Implementation Guide

Authentication and Headers

Nor1 eXpress APIs are exposed through OHIP. As a result, both OHIP gateway requirements and Nor1 eXpress request-context requirements apply. During onboarding, confirm the authentication model and the required request values for each customer environment.

Oracle Hospitality Property APIs support multiple authentication models. In this guide, SSD refers to the Resource Owner Group Authentication model used by some OHIP implementations.

Authentication model reference: Use the Resource Owner Group Authentication (SSD) documentation when the implementation uses the resource-owner group authentication model. Use the Oracle Hospitality Property APIs with Client Credentials Authentication (OCIM) documentation when the implementation uses client credentials with Oracle Cloud Identity Management. Confirm the applicable authentication model during onboarding, as it determines the required credentials and gateway configuration.

Before testing, confirm that the partner's OAuth token credentials are associated with the same OHIP connection used by Nor1 for the target hotel and environment. For hotels that use Oracle Cloud Identity Management (OCIM), follow the Oracle Hospitality Property APIs with Client Credentials Authentication (OCIM) guide and confirm that the required public key or certificate configuration is complete before certification. Use the Resource Owner Group Authentication (SSD) reference when the implementation uses the resource-owner group authentication model. Use the OCIM reference when the implementation uses client credentials with Oracle Cloud Identity Management.

Table 3-5 Authentication and Headers

Header	Required	Source	Notes
Authorization	Yes	OHIP / eXpress API.	Bearer OAuth access token for the target OHIP environment.
x-app-key	Yes for OHIP gateway	OHIP	Developer Portal application key. Required by OHIP Property API conventions.
x-hotelid	Often required by OHIP gateway	OHIP	Hotel ID header used by OHIP Property API calls. Keep aligned with path hotelId when required.
providerId	Optional	Nor1 eXpress API	Provider ID. Defaults to UPS when omitted or blank.
Accept-Language	Optional for GET	Nor1 eXpress API	Language code used when requesting offers.
x-requestid	Optional but recommended	OHIP / eXpress API	Correlation ID for troubleshooting. Responses echo x-requestid and include x-operationid.
Content-Type	Required for POST	HTTP	Use application/json for POST fulfillment.
Accept	Recommended	HTTP	Use application/json.
Security: Do not log or send client secrets, passwords, access tokens, or unnecessary guest personal data in support requests. Renew OAuth tokens before expiry and store credentials securely.

Parent topic: Nor1 eXpress API Implementation Guide

Retrieve Offers

Call GET upsellOffers after identifying the reservation and arrival date.

Table 3-6 Retrieve Offers

Status	Meeting	Integrator action
200 OK	Eligible offer groups returned.	Present offers to the guest and persist the returned offerId only as needed for the current selection flow.
204 No Content	No eligible offers for the reservation, date, room count, or current Nor1 configuration.	Do not show an offer. Continue the guest journey without eXpress API upsell.
400 Bad Request	Missing or invalid path values, date format, or environment setup.	Correct request path values and confirm the OHIP connection and onboarding configuration.
401 Unauthorized	Token expired or invalid.	Refresh OAuth token and confirm application/environment context.
404 Not Found	Booking or offer context not found, including arrival-date mismatch.	Confirm hotelId, reservationId, arrivalDate, and test data.
429 Too Many Requests	OHIP platform throttling may apply.	Back off, reduce request rate, and retry according to integration policy.
500 Internal Server Error	Internal, OPERA/OHIP, or Nor1 processing failure.	Capture sanitized request/response and x-requestid for support.

Parent topic: Nor1 eXpress API Implementation Guide

Offer Response

Successful GET and POST responses use a GenericResponse envelope. The offer groups are returned under items[].upsellOffers[].

{
  "items": [
    {
      "upsellOffers": [
        {
          "offerType": "room_upgrade",
          "selectionType": "zero_to_one",
          "offers": [
            {
              "offerId": "generated-offer-id",
              "name": "Bay View Suite
        King Bed",
              "description": "Offer description",
              "images": {"small":
        "https://...", "big": "https://..."},
              "price": {"amount":
        227.40, "currency": "USD"},
              "savings": 151.60,
              "chargeFrequency": "per_unit_per_night",
              "fixedCharge": 101.82,
              "roomTypeCode": ["7KN"]
            }
          ]
        }
      ]
    }
  ],
  "totalResults": 1,
  "offset": 0,
  "count": 1,
  "hasMore": false,
  "limit": 0
 }

Table 3-7 Offer Response

Field	Description
offerType	Offer family such as room_upgrade, early_checkin, late_checkout, food_beverage, or spa_services.
seelctionType	zero_to_one means selecting one offer expires peer offers in that offer type; zero_to_many supports multiple selections in the group.
offerId	Generated eXpress API offer identifier. Submit this value in POST fulfillment.
price.amount / price.currency	Guest-facing offer price and currency.
chargeFrequency	Charging cadence such as per_unit_per_night or per_unit_per_stay.
fixedCharge	Fixed charge value when supplied by the offer.
roomTypeCode	Room type code list, primarily relevant for room upgrade offers.

Parent topic: Nor1 eXpress API Implementation Guide

Fulfill an Offer

Call POST upsellOffers only after the guest selects an offer returned by GET. The request body contains the offerId.

Table 3-8 Fulfill an Ofer

Fulfillment Rule	Behavior
Offer ID lookup	The service looks up offerId in persisted eXpress API offers. Missing offers return not found behavior.
Reservation match	The offer must match the current property, reservation, and arrival date.
Expired/selected offers	Previously selected or expired offers are rejected as no longer available.
Room type selection	When a room-upgrade offer has multiple room types, the service selects the room type with highest availability.
OPERA/OHIP update	Fulfillment writes the selected offer to OPERA/OHIP as part of the operating model.
Nor1 update	The Nor1 fulfillment update is sent asynchronously after the selected offer is persisted.
zero_to_one groups	Peer offers in the same offer type are expired after a successful selection.

Parent topic: Nor1 eXpress API Implementation Guide

Idempotency, Retries, and Timing

The current eXpress API does not expose a separate idempotency key for POST fulfillment.
Do not automatically retry POST fulfillment without checking the result of the first attempt. A second POST with the same offerId can be rejected after the offer is selected or expired.
If a client times out after POST, use the x-requestid and sanitized request details for support investigation before attempting a guest-visible duplicate action.
Offer IDs should be treated as short-lived values tied to the reservation, arrival date, and current availability state.

Parent topic: Nor1 eXpress API Implementation Guide

Testing and Certification

Table 3-9 Testing and Certification

Scenario	Expected Result
Valid eligible reservation	GET returns 200 and at least one offer group.
No eligible offers	GET returns 204 No Content.
Past arrival date or multi-room reservation	GET returns no eligible offers according to service behavior.
Arrival date mismatch	GET returns booking-not-found behavior.
Invalid or expired token	API returns 401 Unauthorized.
Successful fulfillment	POST returns 200 with selected offer details.
POST wrong reservation/date for offerId	API rejects the offer as invalid/not found.
Repeat POST for selected/expired offer	API rejects the offer as no longer available.
Required Nor1 subscription	The required Nor1 subscription is confirmed before certification testing starts.
Exposure window alignment	Partner API exposure timing matches the Nor1 eXpress exposure window, such as 72, 48, or 24 hours before arrival, and written confirmation is available.
OHIP, OCIM, and certificate readiness	OHIP connection, partner OAuth token credentials, OCIM status, and required public key or certificate configuration are validated before certification.

Parent topic: Nor1 eXpress API Implementation Guide

Troubleshooting

Table 3-10 Troubleshooting

Symptom	Check First	Evidence to collect
Cannot reach gateway	Gateway URL, DNS, TLS, proxy/firewall, allowlisting.	Gateway URL, timestamp, network error, source IP if relevant.
401 or 403	OAuth token, client credentials, scope, x-app-key, API plan subscription, environment mismatch.	Sanitized headers, token issue time/expiry, response code, x-requestid.
400	Path values, mapped OHIP context, onboarding setup, and date format.	Sanitized request path, non-sensitive headers, environment details, and x-requestid.
204 no offers	Nor1 Control Panel setup, reservation eligibility, offer configuration, providerId or property mapping, and arrival window.	Reservation ID, hotel ID, arrival date, providerId, expected eligibility.
404	Reservation exists in target hotel/environment and arrival date matches.	Reservation test data and response body.
POST fails after GET success	OfferId is current, reservation/date match, offer not already selected/expired.	GET response offerId, POST request body, x-requestid.

Parent topic: Nor1 eXpress API Implementation Guide

Production Readiness Checklist

Production Developer Portal application is registered and subscribed to the correct Nor1/OHIP API plan.
Production gateway URL, OAuth credentials, scope, x-app-key, hotel ID, and enterprise/SSD context are configured.
Nor1 Control Panel setup is complete for each hotel and approved offer flow.
Property, chain, enterprise, providerId, and Oracle/Nor1-confirmed property mapping values are confirmed.
Eligible and ineligible test reservations pass certification scenarios.
Guest-facing UI handles 204 no-offer responses without showing an error.
POST fulfillment has duplicate-click protection and timeout handling.
Monitoring captures status code, operation, hotel ID, providerId, timestamp, and x-requestid without secrets or guest personal data.
Support contacts and launch monitoring ownership are agreed.
Required Nor1 subscription is confirmed.
Written confirmation is received for third-party API exposure timing.
Partner OAuth token credentials are associated with the OHIP connection used by Nor1.
OCIM and public key or certificate readiness are confirmed where applicable.

Parent topic: Nor1 eXpress API Implementation Guide

Support Escalation Package

Table 3-11 Support Escalation Package

Information	Include
Environment	Sandbox, UAT, staging, or production; gateway URL used.
Operation	GET offers or POST fulfillment; full path without secrets.
Time	Timestamp with timezone.
Correlation	x-requestid and any OHIP correlation ID returned.
Identifiers	Enterprise ID, chain code, hotel ID, reservation ID, arrival date, and providerId or property mapping if applicable.
Response	HTTP status and sanitized response body.
Request	Sanitized request headers and body. Never include secrets, passwords, or tokens.
Nor1 setup	Confirmation that Control Panel setup and reservation eligibility were checked.

Parent topic: Nor1 eXpress API Implementation Guide

Appendix A Environment Variable Template

GatewayURL=<OHIP gateway URL>

ClientId=<Developer Portal client ID>

ClientSecret=<Developer Portal client secret>

Scope=<OAuth scope>

AppKey=<x-app-key>

HotelId=<hotelId>

EnterpriseId=<enterpriseId, if using enterprise path variant>

ProviderId=<providerId, optional; defaults to UPS if omitted>

RequestId=<client-generated correlation ID>

Parent topic: Nor1 eXpress API Implementation Guide