Integration

The wec360° integration engine is a machine to machine application (M2M) used to collect and transform your unit data into the wec360° ecosystem. It’s based on fetching new data from the source endpoint at fixed intervals.

For an easy integration process, we recommend each of your projects to have a JSON get api endpoint openly available or be using any of the supported authentication methods below. It’s important that each unit has an immutable unique identifier (id/guid) so it can be identified and updated after the initial synchronization.

Your data model is easily transformed into ours using a configuration that contains a mapping table of sorts.

Each field in wec360°:s domain model gets mapped to a field in the endpoints response object using this transform configuration. The units need to be in an array or map that we can iterate. Each unit need to contain all information we should import in a dot notation/tree structure. When iterating the units, information can only be retrieved down the tree structure, not up.

Once you have connected your fields to ours the integration configuration is completed and the data will be pulled from your api at the designated interval and update the units in the wec360° ecosystem.

Supported authentication methods

This is a list of currently supported authentication methods. Custom authentication methods can be implemented on request.

  • Basic authentication
  • Static header key/values
  • Static query string key/values
  • OpenID Connect (OAuth 2)
  • Mom-Api key (Momentum real estate system)

Required information

To establish an integration with the presentation platform, the minimum information required for each unit is:

  • Guid - A unique id for the specific unit
  • Name - the name of the unit
  • Status - for sale, sold, reserved etc.

Example

{
"guid": "abc-123",
"name": "Unit abc-123",
"status": "for_sale"
}

Recommended information

The presentation platform has support for a lot of unit information, and we recommend that you add as much information as possible. Here's a list of the most commonly displayed information:

  • Description - A selling description about the apartment or the project in general
  • Access date - When is the apartment's move-in date?
  • Sales start date - When will you start selling the apartments?
  • Size - How big is the apartment?
  • Rooms - How many rooms does the apartment have?
  • Price - How much does the apartment cost?
  • Monthly fee - How much is the monthly fee of the apartment?
  • Latitude/longitude - Will show the apartments position on google maps

Example

{
"guid": "abc-123",
"name": "Unit abc-123",
"status": "for_sale",
"description": "A lovely apartment in a calm neighbourhood",
"accessDate": "2022-10-10",
"salesStartDate": "2021 - 04 - 01",
"size": "75",
"rooms": "3",
"price": "450000",
"monthlyFee": "450",
"latitude": "59.243756",
"longitide": "15.199185"
}

External linking

In addition to the information above, it is also possible to add three different external links.

extUrl When used, all unit mappings in the platform will link to this url when clicked. This automatically disables the unit view. If the platform is embedded in an iframe, you can choose how you want the external link to behave.

  • Open in a new tab
  • Open in the same frame (iframe)
  • Open in a top frame (will open in the iframes parent, causing the link to behave as if the link was on the same page as the iframe)

extInterestUrl When used, the interest button appears in the unit view. Cannot be used in combination with the extUrl.

extBidUrl When used, the show bid button appears in the unit view. Cannot be used in combination with the extUrl.