HTTP 200

They are two possible HTTP 200 responses by the API:

1. "status": "SUCCESSFUL"

   {
       "status": "SUCCESSFUL",
       "cardType": "ALL Classic",
       "cardTier": "Classic",
       "cardNumber": "30810316065496B8"
   }

   This means either:

   • The customer did not exist in ACCOR's system and he was successfully created and enrolled to the ALL Loyalty Program.
     The customer will receive an email, inviting him to create a password in order to finalize the creation of his/her account.
   • The customer already exists in ACCOR's system but was not yet enrolled to the ALL Loyalty Program, which is the case with this success.
     The customer will receive an email, inviting him to discover the benefits of the program.
2. "status": "EXTERNAl_ID_UPDATED"

   {
       "status": "EXTERNAL_ID_UPDATED",
       "cardType": "ALL Classic",
       "cardTier": "Classic",
       "cardNumber": "30810311093097BH"
   }

   ⚠️ Warning: not all partners can update the external id. if you want to be able to update this id, please ask accor's tech team

   This means that the customer already existed in ACCOR's system and was already enrolled.
   Two possibilities:

   • The account is was not flag as a partner's system user and his externalID is created
   • The account is was flag as a partner's system user and his externalID is updated (only if accepted by ACCOR's tech team)

In the field "cardNumber", you will be given the PMID of the customer, which is the unique ID of the customer throughout the ACCOR IT.

Card number is structured like this 30810311093097BH: 

• 3081031 : product code - determines the type of card the customer has (in this case, this corresponds to ALL Classic card)

• 1093097B: Personal Member ID (PMID)

• H : Luhn key

HTTP 400

There are several cases where the API will return a HTTP 400 error but one of them needs more explainations.

"title": "MEMBER_EXTERNAL_ID_ALREADY_EXISTS"

{
    "title": "MEMBER_EXTERNAL_ID_ALREADY_EXISTS",
    "status": "1231",
    "detail": "Rejected for already existing member external ID",
    "requestId": "be1885d2-5003-49ed-970b-6474f9840353"
}

This can be the symptom of one of two cases:

• The external ID given to the customer was already given to another customer
• The external ID given to the customer is already the one of the customer