Monday, February 12, 2018

New South African portal, Qwengo now live for listing syndication



We have enabled a new Sync listing syndication portal for all our South African real estate users: www.qwengo.co.za

Entegral offers an initial, exclusive interface to the new portal and listings have already been integrated. The portal is free and currently updates listings from the OMS every hour.

If you are using our Sync API http://www.entegral.net/sync/api from your own management system, the new portal can simply be enabled by passing qwengo in the portallistingobject.

Monday, January 22, 2018

OMS API update version 1.10 - Get contacts enhancements




An update has been made for the OMS APIversion 1.10.
It is documented in our OMS API documentation.

Retrieve landlord type contacts 
We now indicate 'landlord' contact types as part of the "category_system" response.
You can furthermore also filter specifically for landlord contact types only. 

https://omsflow.docs.apiary.io/#reference/contact/contacts-collection/view-contacts
Module 4 access is required to retrieve contacts.

New Property ID field
A new field 'property_id' is returned as part of the View Contacts response. This allows you to identify the listings this contact is linked to (if any), e.g.


 {
        "id": 142508,
        "first_name": "John",
        "last_name": "Doe",
        "title": "Mr",
        "mobile_number": "0829998888",
        "office_number": "",
        "email": "johnd@entegral.net",
        "category_system": "landlord",
        "category_user": "",
        "is_office_shared": false,
        "is_active": true,
        "birthday": "1980-01-01",
        "added": "2018-01-07",
        "property_id": "101555"
    }

The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own API keys for web developers. 

Friday, December 22, 2017

OMS API update version 1.9 - Erf No & Block



An update has been made for the OMS APIversion 1.9.
It is documented in our OMS API documentation.

Retrieve Erf No & Block 
You can now retrieve two new fields on individual property calls:
https://omsflow.docs.apiary.io/#reference/property/property-details/view-property
- Erf Number (e.g. 
"location_erfno","1212" )
- Block (e.g. "location_block","A" )
Module 1 access is required.

The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own API keys for web developers. 

Thursday, December 7, 2017

OMS API update version 1.8 - retrieve listing files



An update has been made for the OMS APIversion 1.8.
It is documented in our OMS API documentation.

Retrieve property listing files
You can now retrieve files stored on property listings using:
https://omsflow.docs.apiary.io/#reference/property/property-files

Files retrieved:
1) In the OMS, all files saved and marked as 'public files' 
2) In the OMS, files specifically programmed to be made available through the OMS API. This can include brochures, files marked saved ofr internal access or any other custom programmed files for a specific office. 
Files are made available through URL links and in the case of the programmed files (2) made available for 30 days, after the link will self-destruct.

Module 3 access, which also provides access to notes, is required.


The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own API keys for web developers. 

Friday, November 10, 2017

OMS API update version 1.7 - inactive properties

An update has been made for the OMS API, version 1.7.
It is documented in our OMS API documentation.



Retrieve inactive properties
You can now retrieve properties made inactive for the last 3 months using the following call:
https://omsflow.docs.apiary.io/#reference/property/inactive-properties-collection


Retrieve all property addresses
Under permission https://omsflow.docs.apiary.io/#introduction/authentication we've added a new module 5 "Access all property addresses". This can be enabled in the OMS to provide your developer with access to all property address info (unit number, complex name, street number and street name) for the property details (https://omsflow.docs.apiary.io/#reference/property/property-details/view-property?console=1) irrespective of whether you've checked the 'make map location' checkbox in the OMS for a listing. We've also included a new field 'location_makepublic' to indicate whether the agent has given permission to make the address public.

When module 5 access is included for developer OMS API key, the data can look as follows:

 "location_makepublic": 0,
 "location_streetNumber": "23",
 "location_streetName": "Main road",
 "location_unitNumber": "88",
 "location_complexName": "Petervale Boulevard",

Note although the agent has not selected the 'make map location available' in the OMS (location_makepublic = 0) it will still retrieve the address details through the module 5 access. It should therefor be used with consideration and only for internal system integrations. 
To add module 5 access for an OMS API key, simply create a new key and revoke (delete) the previous key.


The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own API keys for web developers. 

Thursday, November 2, 2017

OMS API updates version 1.6 - Commercial Fields

An update has been made for the OMS API version 1.6.
It is documented in our OMS API documentation.

Over 20 commercial fields has now been added to the property details view. Details can be found here: http://docs.omsflow.apiary.io/#reference/property/property-details/view-property

The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own API keys for web developers. 


Monday, October 30, 2017

OMS API updates version 1.5 - Updated Fields

Herewith a list of enhancements made to the OMS API version 1.5.
It is also documented in our OMS API documentation.


1. The properties collection /properties now includes an updated attribute indicating the last time changes were made to the property listing e.g.
{
        "property_id": 1007346,
        "status": 56,
        "updated": "2017-08-01 09:47"
}


2. The property details call /properties/property_id now includes the update time for each photo. All photos are now also served via HTTPS by default, e.g.
 {
            "url_thumb": "https://s3.entegral.net/p/t1031565_50e78e61-f613-41cb-861e-b45218c360141.jpg",
            "url_large": "https://s3.entegral.net/p/1031565_50e78e61-f613-41cb-861e-b45218c360141.jpg",
            "updated": "2017-09-12 10:17"
        },
        {
            "url_thumb": "https://s3.entegral.net/p/t1031565_034a5e51-65d8-4e45-aaeb-ee65a014e23c1.jpg",
            "url_large": "https://s3.entegral.net/p/1031565_034a5e51-65d8-4e45-aaeb-ee65a014e23c1.jpg",
            "updated": "2017-09-12 10:17"
        },




The OMS API can be used to extract data from the OMS to external systems. It is included free of charge to all clients. Clients can generate their own keys for developers http://productblog.entegral.net/2017/07/generate-your-own-oms-api-keys-for.html