Migration of the endpoint POST /v0/wifi_access_request to POST /v1/wifi_access_request

  • Outdated
  • August 1, 2025
  • 1 related route

Context

Upgrade from POST - /v0/wifi_access_request to POST - /v1/wifi_access_request

Key benefit :

  • Benefit from a new field "phone_number" and optin becomes a list of optins

Impacts

Route to call :

  • POST - /v1/wifi_access_request

Input became

{
  "product_id": "MPAC",
  "customer_information": {
    "first_name": "Jean",
    "last_name": "Smith",
    "nationality": "FR",
    "room_number": "14",
-    "optin": true,
    "social_media": "facebook",
    "email": "jean.smith@something.com",
+   "phone_number": "06030201010",
+   "optins": [
          {
            "channel": "SMS",
            "optin": true
          }
        ],
    "user_language": "fr"
  }
}
filed namefield typeO/FDescriptionExample value
customer_information.phone_numberStringFMobile phone number of the customer requesting a wifi connection.nullable truepattern: "^[+]?[0-9]+$"06030201010
customer_information.optins.channelENUMFCommunication channel [EMAIL, SMS]SMS
customer_information.optins.optinBooleanFTrue if the customer has agreed to be contacted on this channelTrue