Index | Authentication | Offices | Associates | Properties | Property Descriptions | Property Rooms | Property Images
Lookups | Geo data | Files

Property Descriptions

General

Property descriptions are essential in the presentation of a property. In our system you can add different type of descriptions in multiple languages.

The most used description types are ListingTitle (1113) and Web (629). See REXAPI Enumerated Values, Lookup Property_DescriptionType for more descriptions. Not all descriptioins might be available for your specific case. Please discuss with your account manager.

For a better exposure of your listing, please create ListingTitle and Web desccriptions for each property you add to our system.

The list of supported languages that you can use to save your descriptions can be found in REXAPI Enumerated Values, lookup SupportedLanguages.

Supported methods

* All listings are provided as example.They might not contain the entire list of fields. For the complete list of fields, please consult the corresponding data dictionary.

Get list of property descriptions

This method returns the list of all the descriptions for a property.
Response is not paginated, you get all values in one call.

Call

GET integrator/{integrator id}/propertydescriptions/{property id}
property id
ID or ExternalID of a property

Request

GET http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155 HTTP/1.1 

Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk+", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 
Accept: application/xml; charset=utf-8

Response XML

HTTP/1.1 200 OK 
Content-Type: application/xml; charset=utf-8

<RexApiList xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <HasNextPage>false</HasNextPage>
  <HasPreviousPage>false</HasPreviousPage>
  <PageIndex>1</PageIndex>
  <PageSize>3</PageSize>
  <TotalCount>3</TotalCount>
  <TotalPageCount>1</TotalPageCount>
  <Items>
<PropertyDescription> <DescriptionText>Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting, brand new interior/exterior paint and wood shutters throughout! Open floor plan with a living room and an adjacent dining room.</DescriptionText> <DescriptionType>629</DescriptionType> <LanguageCode>ENG</LanguageCode> <ModifiedDate>2014-11-28T10:27:17.497</ModifiedDate> </PropertyDescription> <PropertyDescription> .....
</Items>
</RexApiList>

Response JSON

HTTP/1.1 200 OK 
Content-Type: application/json; charset=utf-8

{ 
 "HasNextPage": false,
 "HasPreviousPage": false,
 "PageIndex": 1,
 "PageSize": 3,
 "TotalCount": 3,
 "TotalPageCount": 1,
 "Items": [
  {
    "LanguageCode": "ENG", 
    "DescriptionText": "Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting,", 
    "DescriptionType": 629, 
    "ModifiedDate": "2014-11-28T10:27:17.497" 
  },
  .....
]
}

Http Status Codes Responses & Messages

Status Message Description
200 - OK You get the list of objects Call was successful
404 - Not Found    

 

Get one property description

This method returns the details of one description

GET integrator/{integrator id}/propertydescriptions/{property id}/{description type}/{language code}

Required parameters:

property id
ID or ExternalID of a property
description type
The UID of the description type. See REXAPI Enumerated Values, Lookup Property_DescriptionType
language code
The language code of the description. REXAPI Enumerated Values, lookup SupportedLanguages

Request

GET http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155/629/ENG HTTP/1.1 

Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk+", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 
Accept: application/xml; charset=utf-8

Response XML

HTTP/1.1 200 OK 
Content-Type: application/xml; charset=utf-8

<PropertyDescription>
   <DescriptionText>Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting, brand new interior/exterior 
paint and wood shutters throughout! Open floor plan with a living room and an adjacent dining room.</DescriptionText> 
   <DescriptionType>629</DescriptionType> 
   <LanguageCode>ENG</LanguageCode> 
   <ModifiedDate>2014-11-28T10:27:17.497</ModifiedDate> 
</PropertyDescription>

Response JSON

HTTP/1.1 200 OK 
Content-Type: application/json; charset=utf-8

{ 
  "LanguageCode": "ENG", 
  "DescriptionText": "Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting,", 
  "DescriptionType": 629, 
  "ModifiedDate": "2014-11-28T10:27:17.497" 
}

Http Status Codes Responses & Messages

Status Message Description
200 - OK You get the resource object Call was successful
404 - Not Found   Resource was not found for the specified ID


Create property description

This method allows you to create a new property description.

Following values from your object model are ignored:

Call

POST integrator/{integrator id}/propertydescriptions/{property id}

Required parameters:

property id
ID or ExternalID of a property

Request XML

In XML, elements order is important. The order is alphabetical.

POST http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155 HTTP/1.1 
Accept: application/xml; charset=utf-8 
Content-Type: application/xml; charset=utf-8 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

<PropertyDescription>
   <DescriptionText>Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting, brand new interior/exterior 
paint and wood shutters throughout! Open floor plan with a living room and an adjacent dining room.</DescriptionText> 
   <DescriptionType>629</DescriptionType> 
   <LanguageCode>ENG</LanguageCode> 
</PropertyDescription>

Response XML

HTTP/1.1 201 Created 
Content-Type: application/xml; charset=utf-8 
Location: http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155/629/ENG

... created Property Description object ...

Request JSON

In JSON, element order does not matter. In our example they are ordered alphabetically just for comparation with the XML response.

POST http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155 HTTP/1.1 
Accept: application/json; charset=utf-8 
Content-Type: application/json; charset=utf-8 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

{ 
  "LanguageCode": "ENG", 
  "DescriptionText": "Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting,", 
  "DescriptionType": 629 
}

Response JSON

HTTP/1.1 201 Created 
Content-Type: application/json; charset=utf-8 
Location: http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155/629/ENG

... created Property Description object ...

Http Status Codes Responses & Messages

Status Message Description
201 - Created You get the created resource object Call was successful
400 - Bad request <Error>
   <Message>
      New resource validation failure. Resource was not created.
   </Message>
   <MessageDetail>
      .....
   </MessageDetail>
</Error>
<MessageDetail> element will contain the reasons why validation failed. Correct the issues and try again.
400 - Bad request <Error>
   <Message>The request is invalid.</Message>
   <ModelState>
      <requestModel>.....</requestModel>
   </ModelState>
</Error>
The object you tried to upload does not match the expected object definition. <ModelState> element will explain where your object do not match the expected model. Please correct the raised issues and try again.
409 - Conflict <Error>
   <Message>
     A description with the same description type and language code already exists! Resource was not created.
   </Message>
</Error>
You cannot have 2 descriptions of the same type and language
404 - Not found <Error>
   <Message>
     No property was found to math the property id. Please create the property before adding descriptions.
   </Message>
</Error>
 

 

Update property description

This method allows you to update an existing description.

Following values from your object model are ignored:

Call

PUT integrator/{integrator id}/propertydescriptions/{property id}/{description type}/{language code}

Required parameters:

property id
ID or ExternalID of a property
description type
The UID of the description type. See REXAPI Enumerated Values, Lookup Property_DescriptionType
language code
The language code of the description. REXAPI Enumerated Values, lookup SupportedLanguages

Request XML

PUT http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005344006-14  HTTP/1.1 
Accept: application/xml; charset=utf-8 
Content-Type: application/xml; charset=utf-8 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

<PropertyDescription>
   <DescriptionText>Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting, brand new interior/exterior 
paint and wood shutters throughout! Open floor plan with a living room and an adjacent dining room.</DescriptionText> 
   <DescriptionType>629</DescriptionType> 
   <LanguageCode>ENG</LanguageCode> 
</PropertyDescription>

Request JSON

PUT http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005344006-14 HTTP/1.1 
Accept: application/json; charset=utf-8 
Content-Type: application/json; charset=utf-8 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

{ 
  "LanguageCode": "ENG", 
  "DescriptionText": "Well maintained single story home on a quiet cul-de-sac. This home offers brand new carpeting,", 
  "DescriptionType": 629 
}

Response

If the update was successful you will get the resource object back with the updated values.
See Get Property method for XML and JSON responses.

Http Status Codes Responses & Messages

Status Message Description
200 - OK You get the updated resource object Call was successful
404 - Not Found <Error>
   <Message>
      Cannot find any resource to update for the supplied ID. Requested operation was not performed
   </Message>
   <MessageDetail>
      PropertyID {0} = {1}, DescriptionType = {2}, LanguageCode = {3}
 </MessageDetail>
</Error>
Resource was not found for the specified resource ID
400 - Bad Request <Error>
   <Message>
      New resource validation failure. Resource was not updated.
   </Message>
   <MessageDetail>
      .....
   </MessageDetail>
</Error>
<MessageDetail> element will contain the reasons why validation failed. Correct the raised issues and try again.
400 - Bad Request <Error>
   <Message>The request is invalid.</Message>
   <ModelState>
      <requestModel>.....</requestModel>
   </ModelState>
</Error>
The object you tried to upload does not match the expected object definition. <ModelState> element will explain where your object do not match the expected model. Please correct the raised issues and try again.


Delete property description

This method deletes a property description

Call

DELETE integrator/{integrator id}/propertydescriptions/{property id}/{description type}/{language code}

Required parameters:

property id
ID or ExternalID of a property
description type
The UID of the description type. See REXAPI Enumerated Values, Lookup Property_DescriptionType
language code
The language code of the description. REXAPI Enumerated Values, lookup SupportedLanguages

Request

DELETE http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155/629/ENG HTTP/1.1 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

Response

HTTP/1.1 204 No Content

Http Status Codes Responses & Messages

Status Message Description
204 - No Content   Call was successful
400 - Bad Request <Error>
   <Message>
     Invalid Property ID. Requested operation was not performed.
   </Message>
</Error>
No property record exists for the supplied Property ID. As a result, the requested operation could not be performed.


Delete all descriptions

This method deletes all descriptions for a property

Call

DELETE integrator/{integrator id}/properties/{resource id}/propertydescriptions/{property id}

Required parameters:

property id
ID or ExternalID of a property

Request

DELETE http://rexapi.gryphtech.com/api/v1/integrator/1005001/propertydescriptions/1005568017-155 HTTP/1.1  HTTP/1.1 
Authorization: OAUTH oauth_token="pfl4PLrrHKChIRoDS2O9Wfoyr1yjKgbEjCxk", api_key="10D35802-C92A-42B3-88FC-A4489A3CD619" 

Response

HTTP/1.1 204 No Content

Status Codes Responses & Messages

Status Message Description
204 - No Content   Call was successful
400 - Bad Request <Error>
   <Message>
      Invalid Property ID. Requested operation was not performed.
   </Message>
</Error>
No property exists for the specified property ID. As a result, the requested operation could not be performed.