SiteMinder APIs
Help CentrePartner ContactsTest Extranet LoginBecome a SiteMinder Partner
  • Hub
  • Quickstart
  • Integration Process
  • CHANNELS
    • Introduction
      • SiteConnect
        • Getting Started
        • Developer Guide
          • Integration Requirements
          • Message Structure
          • Error Handling
        • API Reference
          • Rooms and Rates
          • Availability and Restrictions
          • Rates
          • Reservations
            • Reservation XML Sample
        • Testing and Certification
        • Changelog
        • FAQ
      • Channels Plus
        • Getting Started
        • Developer Guide
          • Partner Portal
          • Deals
          • Invoicing: Gross vs. Net
        • API Reference
          • Properties
          • Property
          • Lock Reservation
          • Confirm Reservation
          • Modify Reservation
          • Cancel Reservation
        • Testing and Certification
        • Swagger
        • Changelog
        • FAQ
  • PMS / RMS
    • Introduction
      • pmsXchange
        • Getting Started
        • Developer Guide
          • Integration Requirements
          • Message Structure
          • Error Handling
        • API Reference
          • Rooms and Rates
          • Availability and Restrictions
          • Rates
          • Reservations
            • Reservations PULL
            • Reservations Import
            • Reservations Upload
              • Reservation Types
            • Payment Transaction Record
            • Credit Card Tokenization
            • Reservations XML Samples
              • Reservations PULL Samples
              • Reservations Upload Samples
        • Testing and Certification
        • Changelog
        • FAQ
  • APPS
    • Introduction
      • SiteMinder Exchange
        • Getting Started
        • Developer Guide
          • Integration Requirements
          • Message Structure
          • Error Handling
        • API Reference
          • Availability and Rates
            • Publishers
            • Hotels
            • RoomTypes
            • RatePlans
            • Availability
            • Rates
            • Models
            • Response Samples
              • Publishers Sample
              • Hotels Sample
              • RoomTypes Samples
              • RatePlans Samples
              • Availability Samples
              • Rates Sample
            • ARI 1-Way Guidelines
          • Reservations
            • Maximum Content Sample
            • Minimum Content Sample
        • Testing and Certification
        • Activation & Deactivation Process for Hotels
          • Activation Process for Hotels
          • Activation Form Parameterisation
          • Deactivation Process for Hotels
        • Changelog
          • Reservations API Changelog
          • ARI API Changelog
        • FAQ
  • Additional Resources
    • Reference Tables
      • Booking Agent Codes
      • Document Type Code (DOC)
      • Error Codes (ERR)
      • Error Warning Types (EWT)
      • Fee Tax Type (FTT)
      • Handling HTTP 500
      • Meal Plan Type (MPT)
      • OpenTravel Codes List
      • Payment Card Provider Codes
      • Service and Extra Charge
      • Strong Customer Authentication Codes
      • Test Credit Cards
    • Glossary
    • FAQ
Powered by GitBook
On this page

Was this helpful?

  1. APPS
  2. Introduction
  3. SiteMinder Exchange
  4. Activation & Deactivation Process for Hotels

Activation Process for Hotels

Last updated 5 months ago

Was this helpful?

Here are the steps for the Onboarding Property Activation that hotels can follow once your application is live with SMX.

If your Application requires Support Escalation or direct communication with the Publisher (PMS) regarding an issue, contact to open a support case and we will provide you with the Publisher’s contact details.

The Application can use our Test Activation form for testing purposes.

Hotel Steps

  1. The hotel fills out the Activation form located at

    1. The application should provide the hotel with their application property code so they can complete the form. The subscriber/application hotel code is the hotel ID the application has assigned for the hotel account in their system. SMX Team will not provide this code.

    2. If the hotel makes a request for an incorrect Publisher (PMS) or Subscriber (application), they must fill out the request form again.

  2. The hotel is given a request number once the form has been submitted.

Application and SMX Teams Steps

  1. The form details go straight into our SMX Admin Portal and will be in Pending status. The SMX Activations Team will receive a notification.

  2. Activation is just a click of a button. The SMX team will send the app an email first to confirm property and application hotel code is correct before the activation.

  3. Once activated, if your application requires a flush of historical (past) reservation data, then we can push for a selected time period: 3 months, 6 months, 1 year etc. The time period is based on the creation date (booked on) of the reservation so this might include future reservations that were created in the selected time frame.

    1. At the moment, we are not able to push reservations based on the Check-In date only.

  4. We will send a small flush, check the logs to confirm we received successful responses (no errors) and ask the application to confirm receipt of the reservations. After confirmation, we will send the full flush for the selected time-period.

  5. If your application also requires ARI data from the Publisher (PMS), you can use our Production ARI endpoint: and the Get queries you certified for to obtain availability and rates data.

At the moment, you are not able to obtain ARI data from the following Publishers: Little Hotelier and SiteMinder Channel Manager.

For any clarification or other request, contact to open a support case.

smx.support@siteminder.com
https://smx-core-activation.dev.siteminderlabs.com/
https://activation.siteminder.services/
https://exchange-api.siteminder.com/inventory/v1
smx.support@siteminder.com