Types and Usage Recommendations

The currently supported Async API operations are listed below.

Note:

Ensure you are following the best practices when calling Asynchronous APIs.

The Asynchronous APIs can be classified into two types according to how they interact with OPERA Cloud:

  1. Operations that fetch Data from OPERA Cloud. This is applicable to the following operations along with the limits specified below:
    Operation ID  Functionality Limit OPERA Cloud Version Dependencies (if any) Recommendations

    Module: Inventory (INVASYNC)

    startRevenueInventoryStatisticsProcess (POST) getRevenueInventoryStatisticsProcessStatus (HEAD) 

    getRevenueInventoryStatistics (GET)

    • Enables you to retrieve Revenue Inventory Statistics

    • You can use this API to fetch revenue inventory statistics for past, present, and future reservations from OPERA Cloud. You will be able to filter using stay date (with a start and end date) to fetch inventory data.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • Current date range limit: 400 days (Refer to the OPERA Cloud Version Dependencies column for more details.)

    • Responses exceeding 2 MB are automatically truncated by the API.

    • With the OPERA Cloud versions 22.1  and higher, the getRevenueInventoryStatistics API response includes values for roomSold, projected roomRevenue, roomArrival, roomDeparture, and projected totalRevenue for reservations with arrival date same as the property business date.

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With the OPERA Cloud versions 23.2 and higher, the maximum date range allowed per request is extended from 94 to 400 days.

    • With the OPERA Cloud versions 24.1 and higher, the getRevenueInventoryStatistics operation includes distributed revenue in its response.

    • With the OPERA Cloud versions 24.2.1 and higher, the cancelledRooms field in the getRevenueInventoryStatistics operation response excludes reservations with pseudo-room types, regardless of whether the reservations pertain to past, current, or future dates.

    • This API is suitable for retrieving future inventory data and calculating net revenue. You can group the data either by Room Type, Market Code, or Guarantee Code (Reservation Type) or you can gather data per date for the entire hotel.

    startInventoryStatisticsProcess (POST)

    getInventoryStatisticsProcessStatus (HEAD)

    getInventoryStatisticsAsync (GET)

    Enables you to retrieve hotel inventory statistics for a specified date range (up to 365 days) provided in the request.

    Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    Current date range limit: 365 days.

    This operation has been added with the OPERA Cloud versions 25.1 and higher.

    Module: Blocks (BLKASYNC)

    startBlockAllocationSummaryProcess (POST)

    getBlockAllocationSummaryProcessStatus (HEAD) 

    getBlockAllocationSummary (GET)

    • Enables you to retrieve Block Allocation Summary

    • You can use this API to fetch Block allocation information for a hotel and specified date range. The block allocated inventory, rates, and room type statistics, including revenue, are returned as part of the response.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • When requesting data with startDate/endDate, the maximum date range allowed per request is 94 days. 

    • When requesting data with startLastModifiedDate/endLastModifiedDate, the maximum date range allowed per request is 3 days. 

    • When requesting data with startLastModifiedDate/endLastModifiedDate, subsequent identical requests (with the same query parameters) must be spaced 3 hours apart. Note that this limit only applies to identical POST requests made without completing the entire POST, HEAD, and GET cycle.

    • Responses exceeding 2 MB are automatically truncated by the API.

    • With the OPERA Cloud versions 21.5 and higher, the getBlockAllocationSummary API response will include values for ownerCode, cutOffDays, cutOffDate, blockType, all status blocks, cancellationDate, and extraPerson values. 

    • With the OPERA Cloud versions 22.1 and higher, the getBlockAllocationSummary API response has been enhanced to include block daily and total revenue statistics.

    • With the OPERA Cloud versions 22.4 and higher, a new search filter lastModifiedDate has been added to the startBlockAllocationSummaryProcess API operation to get the data modified after the previous fetch request.

    • With the OPERA Cloud versions 22.4 and higher, when requesting data with startLastModifiedDate/endLastModifiedDate, subsequent identical requests (with the same query parameters) must be spaced 3 hours apart. Note that this limit only applies to identical POST requests made without completing the entire POST, HEAD, and GET cycle.

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With OPERA Cloud versions 23.3 and higher, the getblockAllocationSummary API response will include origin code.

    • With OPERA Cloud versions 24.2 and higher, the getBlockAllocationSummary includes the "hotelId" field, indicating the corresponding resorts.

    • With OPERA Cloud versions 24.2 and higher, every identical request (employing the same query parameters) for the  getBlockAllocationSummary operation when requesting data with startLastModifiedDate/endLastModifiedDate, necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With OPERA Cloud versions 24.2 and higher, the getBlockAllocationSummary returns the Profile Name for the Company profile and/or Travel Agent Profile on the Block in the response.

    • With OPERA Cloud versions 25.1 and higher, the getBlockAllocationSummary includes the currency element at the block level.
    • With OPERA Cloud versions 25.2 and higher, the getBlockAllocationSummary operation supports a new request body element, includeNetRates, which is false by default. Setting it to true displays net room revenue for the business block directly below the standard rates in the response.

     

    Module: Reservations (RSVASYNC)

    startReservationsDailySummaryProcess (POST)

    getReservationsProcessStatus (HEAD)

    getReservationsDailySummary (GET)

    • Enables you to retrieve Reservation Daily Summary

    • This API allows external systems to retrieve a summary of reservations for a specified hotel and date range.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • When requesting data with startDate/endDate or startLastModifiedDate/endLastModifiedDate, the maximum date range allowed per request is 94 days (whether it is in the past or the future).

    • When requesting data with startLastModifiedDate/endLastModifiedDate, subsequent identical requests (with same query parameters) will have to be spaced 3 hours apart. Note that this limit only applies to identical POST requests made without completing the entire POST, HEAD, and GET cycle. 

    • Responses exceeding 2 MB are automatically truncated by the API.

    • With the OPERA Cloud versions 22.4 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With the OPERA Cloud versions 22.4 and higher, a new search filter lastModifiedDate has been added to the startReservationsDailySummaryProcess operation to get the data modified after the previous fetch request.

    • With the OPERA Cloud versions 22.4 and higher, when requesting data with startLastModifiedDate/endLastModifiedDate, subsequent identical requests (with same query parameters) will have to be spaced 3 hours apart. Note that this limit only applies to identical POST requests made without completing the entire POST, HEAD, and GET cycle. 

    • With the OPERA Cloud versions 22.4 and higher, the getReservationdailySummary API response will include a reservation's net room rate amount.

    • With the OPERA Cloud versions 24.1 and higher, the getReservationDailySummary async operation in the RSV Async API includes the reservation external reference in the response should a reservation have an external reference on it in OPERA Cloud.

    • With OPERA Cloud versions 24.2 and higher, the getBlockAllocationSummary includes the "hotelId" field, indicating the corresponding resorts.

    • With OPERA Cloud versions 24.2 and higher, every identical request (employing the same query parameters) for the getReservationsDailySummary operation when requesting data with startLastModifiedDate/endLastModifiedDate, necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With OPERA Cloud versions 24.3 and higher, the getReservationsDailySummary operation has been enhanced with performance improvements to handle large volumes of reservation data more efficiently. This improvement will result in optimal retrieval of the Reservation Daily Summary for specified properties and date ranges.

    • With OPERA Cloud versions 24.3 and higher, the getReservationsDailySummary operation supports retrieving reservations with special characters in the profile section of the reservation payload.

    • Prior to OPERA Cloud version 25.1.3.0, the membership card number does not support special characters such as ", |, , /, [, or ]. If your data includes these characters, refer to this Customer Support Portal knowledge article for resolution steps. Starting with OPERA Cloud versions 25.1.3.0 and higher, these special characters are supported in membership card numbers.

    • This API is suitable to get a summary of all reservations at a hotel when onboarding a new property with your integration.

    • Data can be requested using either startDate/endDate or startLastModifiedDate/endLastModifiedDate. It is recommended to use the startLastModifiedDate and endLastModifiedDate parameters to retrieve incremental updates since the last call.

    • When requesting data with startLastModifiedDate/endLastModifiedDate, it is recommended to complete all sets of calls (POST, HEAD, and GET) before making new data requests. 

    • Note that if there are no reservations that match the specified criteria for the date range (fixed dates or last modified), it is possible to receive an empty response, indicating no reservations found.
  2. Operations that POST Data to OPERA Cloud. This is applicable to the following operations along with the limits specified below:
    Operation ID (RTPASYNC) Functionality Limit OPERA Cloud Version Dependencies (if any) Recommendations

    Module: Rate Plan

    startSetDailyRatePlanSchedulesProcess (POST)

    getDailyRatePlanSchedulesProcessStatus (HEAD)

    getDailyRatePlanSchedules (GET)

     

    • Enables you to create Daily Rate Plan Schedules

    • You can use this API to add and/or update the rate price schedule to existing OPERA Daily Rate plans.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • While you can update multiple Daily Rate Plan schedules for a given property, you can only update rates for only one property at a time. Refer to About Rate Codes in the OPERA Cloud Services User Guide for more information on rate structures.

    • You can update rates up to 365 days into the future. 

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload.  

    • Optimal payload size: 2 MB

     

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With the OPERA Cloud versions 24.3 and higher, the startSetDailyRatePlanSchedulesProcess operation supports two new elements - rateDateRangeStart and rateDateRangeEnd with date format (YYYY-MM-DD) - to define the date range for applying daily rate amounts.
    • With the OPERA Cloud versions 24.4 and higher, the specs of the operation startSetDailyRatePlanSchedulesProcess have been updated to reflect the latest limits and recommendations.
    • With the OPERA Cloud versions 24.4 and higher, the startSetDailyRatePlanSchedulesProcess operation supports a new request body element - rateByAgeBuckets - which is applicable when the Child Rates by Defined Buckets OPERA Control is enabled and child rate buckets are properly configured.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startSetBestAvailableRatePlansProcess (POST)

    getBestAvailableRatePlansProcessStatus (HEAD)

    getBestAvailableRatePlans (GET)

    • Enables you to create Best Available Rate Plans by Length of Stay or by Day.

    • You can use this API to post new or update existing Best Available Rate by Length Of Stay or by DAY to OPERA Cloud.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload.  

    • Optimal payload size: 100 KB

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startHurdleRatesProcess (POST)

    getHurdleRatesProcessStatus (HEAD)

    getHurdleRates (GET)

     

    • Enables you to create Hurdle Rates.

    • You can use this API to create Hurdle Rates in OPERA Cloud by date.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload.   

    • Optimal payload size: 100 KB

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startRatePlanRoomTypesModifyProcess (POST)

    headRatePlanRoomTypesModifyProcessStatus (HEAD)

    getRatePlanRoomTypesModifyProcessSummary (GET)

    Enables you to add or remove the Room Types to or from rate codes.

    Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    This operation has been introduced with OPERA Cloud versions 25.1 and higher.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Availability (PARASYNC)

    postRestrictionsProcess (POST)

    getRestrictionsProcessStatus (HEAD)

    getRestrictions (GET)

    • Enables you to create Restrictions.

    • A user can send various restrictions to OPERA Cloud by specifying restriction details in the request. You can set restrictions for a whole year and have multiple restrictions on a given day.  However, there can be a hierarchy of restrictions. 

    • Refer to Managing Restrictions in the OPERA Cloud Services User Guide for more information.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload.   

    • Optimal payload size: 2 MB

    • With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • With the OPERA Cloud versions 24.4 and higher, an error is returned if a mandatory field is missing in the getRestrictions operation.
    • With OPERA Cloud versions 24.4 and higher, the postRestrictions operation will be updated to prevent the creation of house-level restrictions when invalid room types or rate codes are present in the request.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Inventory (INVASYNC)

    postSellLimitsProcess (POST)

    getSellLimitsProcessStatus (HEAD)

    getSellLimits (GET)

    • Enables you to create Sell Limits

    • You can use this API to create sell limits in OPERA Cloud by date. Refer to Sell Limits in the OPERA Cloud Services User Guide for more information.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload. 

    • Optimal payload size: 2 MB 

    With the OPERA Cloud versions 22.5 and higher, every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Blocks (BLKASYNC)

    startShiftBlockProcess (POST)

    getShiftBlockProcessStatus (HEAD)

    getShiftBlockProcessInfo (GET)

    Provides the ability to shift block dates for a business block with rooms inventory or events or both.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload. Optimal payload size: 2 MB. 

    This operation has been introduced with OPERA Cloud versions 24.2 and higher.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startAllocationRangesProcess (POST)

    getAllocationRangesProcessStatus (HEAD)

    getAllocationRangesProcessInfo (GET)

    Enables you to update inventory and rates across multiple dates and/or room type range combinations on the block room and rate grid.

    Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    If an existing inventory or rate record is modified while the asynchronous process is running, a message will notify you that the record is currently in use.

    The request payload size that an API user can upload is restricted to 2 MB.

    The getAllocationRangesProcessInfo operation has been added with the OPERA Cloud versions 24.1 and higher.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startRecalculateRoomForecastProcess (POST)

    getRecalculateRoomForecastProcessStatus (HEAD)

    getRecalculateRoomForecastProcessInfo (GET)

    		 Enables recalculation of the room forecast on the room and rate grid whenever there is a change impacting forecasted revenue.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload.

      Optimal payload size: 2 MB

    		The getRecalculateRoomForecastProcessInfo operation has been introduced with the OPERA Cloud versions 25.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Reservation (RSVASYNC)

    startRoomingListValidationProcess (POST)

    getRoomingListValidationProcessStatus (HEAD)

    getRoomingListValidationProcessResults (GET)

    		 Enables you to validate Reservations Rooming List.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    		 This operation has been introduced with the OPERA Cloud versions 23.5 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startReservationDetailsMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to update several reservation details for multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can update the reservation details (Source Code, Market Code, Expected Time of Arrival, Expected Time of Departure, Origin Code, Expected Return Time, Expected Return Time Comments, as well as Reservation UDF Character, Number and Date fields) for up to 100 reservations with a single request.
    • This operation has been introduced with the OPERA Cloud versions 24.1 and higher.
    • With OPERA Cloud versions 24.4 and higher, the startReservationDetailsMassUpdateProcess operation supports the following new request body elements:
      • arrivalDate - Guest check-in date
      • numberNights - Total nights of stay
      • departureDate - Guest check-out date.
      • adults - Number of adults
      • children - Number of children
      • ageOfChild - Age(s) of child guests
      • rateCode - Rate plan code
      • rate - Nightly rate amount
      • roomType - Room type being booked
      • roomTypeToChange - New room type for modifications
    • With OPERA Cloud versions 24.5 and higher, the startReservationDetailsMassUpdateProcess operation includes a new request element, packageCodes, to enable package updates during mass reservation changes.
    		 Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startTracesMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to add a trace to multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can add a trace by specific date, date range, arrival date, or stay dates of the selected reservations for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startPreferencesMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to add a preference to multiple reservations as well as their associated profiles.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can add a preference for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startRoutingInstructionsMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to add routing instructions to multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can add routing instructions (room and/or folio) for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startHousekeepingMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to add/update a housekeeping task schedule for multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can add a housekeeping task schedule or update Room Instructions, Priority, Turndown, and Cleaning time for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startNotesMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to add a reservation note to multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can add a reservation note for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startTransportationsMassUpdateProcess (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to update Transportation for multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can update Arrival and Departure Transportation routing instructions for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startPaymentInstructionsMassUpdateProcess

    (POST)

    headMassUpdateProcessStatus (HEAD)

    getMassUpdateProcessSummary (GET)

    		 Enables you to update payment instructions or add a non-credit card payment type to multiple reservations.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • You can update payment instructions (No-Post, Pre-Stay Charging, and Post Stay Charging) or add a non credit card payment type for up to 100 reservations with a single request.
    		This operation has been introduced with the OPERA Cloud versions 24.1 and higher. Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    startRoomingListCreationProcess (POST)

    getRoomingListCreationProcessStatus (HEAD)

    getRoomingListCreationProcessResults (GET)

    Enables you to create multiple block reservations in OPERA Cloud for a specific block as well as match the associated names with existing profiles.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload. Optimal payload size: 2 MB. 

    This operation has been introduced with OPERA Cloud versions 24.1 and higher.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Profiles (CRMASYNC)

    stayRecords (POST)

    getStayRecordsProcessStatus (HEAD)

    getStayRecordsProcess (GET)

    Allows you to import Stay Records for a profile.

    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.

    • The primary and only limitation in this process is related to the payload size that the API user intends to upload. Optimal payload size: 2 MB. 

    This operation has been introduced with OPERA Cloud versions 24.2 and higher.

    Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.

    Module: Cashiering (CSHASYNC)

    startFinancialPostingsAsync (POST)

    getFinancialPostingsProcessStatusAsync (HEAD)

    getFinancialPostingsAsync (GET)

    		 Enables you to retrieve financial postings with their detailed net VAT breakdown.
    • Every identical request (employing the same query parameters) necessitates a mandatory 30-minute interval between submissions. Please note that this limit applies regardless of whether the POST, HEAD, and GET cycle has been completed.
    • This operation requires the mandatory parameters hotelId, reservationId, startDate, and endDate and supports optional parameters such as folioWindowNo, includePseudoRooms, and duration.
    • The maximum permissible range between the start and end dates is 15 days.
    		 This operation has been introduced with OPERA Cloud versions 25.1 and higher.
    • Operate on a first-come, first-served basis. Data submissions are processed in the order they are received, and the only constraint lies in ensuring that the payload adheres to the specified size guidelines.
    • The operation is recommended for detailed breakdowns of gross and net amounts for the following scenarios:
      • Postings using transaction codes inclusive or exclusive of taxes.
      • Package Wrapper with no-allowance packages.
      • Package Wrapper with allowance packages and full consumption.

Parent topic: Workflow