New Imovirtual

📘

This information is valid only for Imovirtual Partners, already successfully integrated

Soon, you will discover the new Imovirtual, so for now, let's take a look at some impactful changes on API integration:

1. Handling Suspended Accounts:

• Change: Moving forward, user accounts may be suspended if no payment is received. This means suspended accounts can no longer publish or update ads.
• Implication: Suspended accounts will have limited options: Delete and Deactivate ads via API.
• Action Required: If a POST or PUT request is sent for a suspended account, your system will receive an error notification via webhook for following the advert_posted_erroror advert_put_errorevent types. Display this message to the user and do not suspend new oncoming requests, as this user may activate the account at any moment.

🚧

There's no account status notification, only a notification when the request (POST or PUT) is not possible to be succesfully executed.

"data": {
    "data": {
      "detail": "Adding the ad failed.",
      "title": "AdvertsPostingException",
      "validation": [
        {
          "detail": "Utilizador suspenso",
          "field": "user/type",
          "title": "Error"
        }
      ]
    },
    "destination": "",
    "error_message": "Adding the ad failed.",
    "event_timestamp": 1713887667893,
    "event_type": "advert_posted_error",
    "flow": "publish_advert",
    "object_id": "[object_uuid]",
    "timestamp": 1713887667893,
    "transaction_id": "[transaction_id]"
  },

2. Ads Status Migration: Outdated_by_package:

• Change: The ads status "Outdated_by_package" will be migrated to "Outdated".
• Implication: Ads with the status outdated can be updated but will remain unpublished.
• Action Required: Update your system to handle ads in the "Outdated" status, allowing for editing (PUT), activation (ACTIVATE), or deletion (DELETE).

3. Removal of vacation categories:

• Change: Categories *-for-vacation will be removed from Imovirtual, and publishing adverts in these categories will no longer be possible.
• Implication: If you keep sending us after May 6 adverts to these categories, an error message via webhook will be generated as-is when the category does not exist.
• Action Required: Please refrain from sending ads related to houses-for-vacationand apartments-for-vacation after May 6.

"data": {
    "data": {
      "detail": "Bad Request",
      "title": "MercuryCategoryException",
      "validation": [
        {
          "detail": "Categoria é inválida",
          "field": "category_urn",
          "title": "Error"
        }
      ]
    },
    "destination": "",
    "error_message": "Bad Request",
    "event_timestamp": 1713888026615,
    "event_type": "advert_posted_error",
    "flow": "publish_advert",
    "object_id": "[object_uuid]",
    "timestamp": 1713887667893,
    "transaction_id": "[transaction_id]"
  },

4. Taxonomy Parameter Updates:

• Change: New parameters will be available in the Taxonomy API endpoint after May 6.
• Implication: Backward compatibility will be maintained initially, allowing time for system updates after May 6.
• Action Required: Check Taxonomy API later to enable extra parameters.