Useful

Changelog

Here you can find our latest and planned releases.

September 2016

  • Expose API: „realtorValuationJSONLink“, „realtorValuationV2JSONLink“ and „realtorValuationV2JSONPLink“ are not available anymore and disappear from the Expose API response completely. 

 

July 2016

  • Import/Export API: New mandatory field "name" for real estate projects (Sandbox and Live: 27.07.2016) - concerns XSD schema

 

April 2016

  • Import/Export API: new field "customLowestBid" in real estate type compulsoryAuction. Overwrites the existing and calculated field "lowestBid" (Sandbox: 20.04.2016 and Live: 21.04.2016) - concerns XSD schema
  • Import/Export API: free text fields (descriptionNote, furnishingNote, locationNote and otherNote) increased max length from 2000 to 3999 characters (Sandbox and Live: 13.04.2016) - concerns XSD schema

November 2015

  • Bugfix schema: changed type "href" from "xs:anyURI" to "xs:string" to provide a consistent PUT Attachment (Sandbox: 11.11.2015; Live: 12.11.2015) - concerns XSD schema

 

September 2015

REALESTATE-API: we will discontinue supporting "Vollabgleich" from 1.11.2015. "Vollabgleich" is the process of deleting all ressources and creating these very ressources as new ressources as a daily routine. Some clients use this for synchronizing realestates and/or attachments. There are several disadvantages based on this procedere and above that our customers will face costs using "Vollabgleich" if they use ontop placement bookings based on real estates, then these bookings will be gone, if a real estate has been deleted by "Vollabgleich".

We will not discontinue deleting of real estates itself, but will block "Vollabgleich", only.

 

ATTACHMENT-API: From 23.12.2015 we will also discontinue supporting the "Vollabgleich" for picture attachments. Since 25.09.2015, we offer a field"externalchecksum" in the ATTACHMENT-API  which can be used for getting the information, if an attachment has changed. If you use "Vollabgleich" in order tochange the attachments order, than read the documentation because we offer support for your attachment id within the ATTACHMENTORDER-API.

 

Realestate API: attribute „realEstateProjectId“ will be deleted

We will delete the attribute <realEstateProjectId> from the response of GET REALESTATE BY ID on 31.10.2015. The reason for that is, that this information can be gathered from this API: http://api.immobilienscout24.de/our-apis/import-export/realestateproject/entry-get-all.html. If you need to use this API with your own real estate id instead of the IS24 object id, than please send us an email to service@immobilienscout24.de and if there is enough demand, we will enhance that API.

 

Realestate API: attribute "constructionYear" is not mandatory anymore

Until recently, the attribute "constructionYear" was mandatory for the realestate type "investment". From now on, this attribute is optional.

 


August 2015

Import Export API: change attachment order by external id

On this page you’ll find a tutorial about how to change the picture order, without having to save the Immobilienscout24 picture IDs. You can work with your own picture IDs and you don’t need to perform a picture “Vollabgleich” in order to only change the order.

 

Import Export API: You can display pictures in the object overview

Actually, the GETALL REALESTATE response doesn’t contain a picture url. Now, you can add a picture to the object overview in your application by simply adding this parameter „?features=withAttachments“. Therewith, each list entry contains a picture url. Learn more about it

 

Import Export API: Status „archived“ will not be handed out anymore

We have analyzed the usage of the status „archived“ within GET REALESTATE requests and the result is, that it is not being used. „archived“ is not connected with functionalities, it’s just a label for real estates which are deactivated over a longer period of time. Since we don’t offer archiving a real estate by API, we’ve decided to delete this attribute. Therewith, the remaining status are „active“ and „inactive“.

 

Fixed Bugs

  • POST REALESTATE: error message "Contact invalid" (17.8)
  • PUT CONTACT: Error code „500“ (26.8)
  • REALESTATE: „Lastrefurbishment“ is “integer” in xml schema, but “date“ in the error message (21.8)
  • GET REALESTATE: „constructionYearUnknown“ is handed out, although „constructionYear“ has a value (25.8)
  • POST REALESTATE: trade site price interval type: only „Year“ is accepted (6.9): it’ll remain that way, we’ll adjust documentation and schema.

June 2015

HTTPS: After extensive testing, we will set HTTPS mandatory for 3-legged oAuth requests on 30th June on the productional environment and on the 1st July on the sandbox environment.

We have added HTTPS for oAuth requests in a new version of the php-, dotNet- and java sdk. If you use these sdks, please upgrade to the latest version. If you don't use an sdk, then please add HTTPS to your oauth requests.

We will support http for 3-legged oAuth requests until 23.12.2015.

Generally, we advise using https for all api requests, not only for oAuth.

 

Bestellerprinzip: From 01.06.2015 the law named "Bestellerprinzip" has come into effect. Therefore, we don't show the courtage fields in result list and expose on immobilienscout24.de and we have set the value for the courtage field on "no information" in the search and expose api, so that the other 2 courtage fields are not handed out. Therewith, all api-based clients like realtor websites don't have to make any adjustments. This counts only for the relevant real estate types, which are: appartment rent, house rent, sort time living and flat share room.


May 2015

Attachment-API: The sum of the picture and pdf files has been upgraded from 30 to 150 files.

Also, we have raised the file size for picture and pdf files from 10 to 50 MB. Videos remain unchanged: one video of maximum 1 GB.

 

Import-Export-API: Improvements for video upload

we now hand out the field „processingProgress“ in the response of GETBYID Attachment. This number shows the converting status as the video is being processed. If you implement this field, than you don’t need to check if the video if the video processing is done, steadily.

 

Search-API: search filter „number of persons“ („Personenzahl“) will be deleted

This concerns only the realestate type „shortTimeLiving“. The filter will be deleted on 30th July 2015. If you use this filter, than please replace it with the new search filter „numberofrooms“ (Zimmerzahl). Learn more about it.

 

Contact-API: "salutation" has been added

We have enhanced the API for sending contact requests by the attribute „salutation“.

 

Changes to response header

We have made another change in the response header in order to gain more information for processing support requests: the "L-IS24-Requestrefnum" is a UUID and not a randomID anymore  ("67290" -> "cbbb9143-3828-4e02-b0b1-753bc3021245").


March 2015

  • Bug: POST Video Attachment (Video) fails in case of using the static URL http://csp.picsearch.com/upload. Please use always the "uploadUrl" from GET /videopluadticket. - POST Attachment
  • PHP-SDK: added GET Publish (Sandbox and Live) - Github-Commit-URL

 

February 2015

  • PHP-SDK: added get/put attachment order (Sandbox and Live) - Github-Commit-URL
  • PHP-SDK: added put attachment for metadata (e.g. title) (Sandbox and Live) - Github-Commit-URL
  • PHP-SDK: added delete contact (Sandbox and Live) - Github-Commit-URL

 

January 2015

  • PHP-SDK: added attachment upload for URL (Sandbox and Live) - Github-Commit-URL
  • PHP-SDK: added added attachment upload for streaming video (Sandbox and Live) - Github-Commit-URL
  • PHP-SDK: added a parameter with which you can use new EnEv enums for "energySource" (Sandbox and Live) - Github-Commit-URL
  • PHP-SDK: added deletebylist for ontop placements (Sandbox and Live) - Github-Commit-URL

 

November 2014

  • REST-Import-API: GET Video attachment has been enhanced by 2 urls: one for accessing the video without our player and one for accessing a picture which is the first still image of the video. (Sandbox and Live) - documentation - new XSD schemes
  • REST-Import-API: we have enhanced the CONTACT-API by 2 attributes which we only use for the realtors profile page in the IS24 "Branchenbuch" (= a IS24 yellow pages for realtors): "position", and "showOnProfilePage". With the 2nd attribute we solve the problem, that an update on a contact address overwrites the profile page allocation. (Sandbox and Live) - documentation - concerns XSD schema
  • Since 27.11.2014, we neither support flat share rooms (WGs) by REST API nor by online editing (ScoutManager). You can still deactivate (DELETE PUBLISH) flat share rooms by REST-API. We have moved this real estate type to the platform http://www.wg-suche.de where you can publish flat share rooms for free.
  • PHP-SDK: Authentication without MySQL databases
    We have enhanced the PHP-SDK so that a user can be authenticated without using a MySQL database. Additionally, saving something in the database is decoupled from a session.
  • REST-Import-API: OnTop: In GETall response you can find the "externalId" after the field "servicePeriod". (Sandbox and Live) - documentation
  • API status is shown in the developer center. Momentarily, we offer this feature for the Import-/Export-API only. However, it will be enhanced by other APIs. The availability check does not only check the availability of the API itself, but also the complete process including database availability.  
  • REST-Import-API: OnTop: DELETEbyList OnTop Placement is possible now. (Sandbox and Live) - documentation
  • JAVA-SDK: Building projects and special placement APIs added - documentation

 

October 2014

REST-Import-API: Publish: DELETEbyList Publish is possible now. (Sandbox and Live) - documentation

 

September 2014

  • REST-Import-API: OnTop: POST/GET/PUT/DELETE of the new OnTop Placement ressources "showcaseplacemt" and "topplacement" possible. (Sandbox and Live) - documentation - new XSD schemes
  • Bugfix: Reduce Internal Server Errors (Status code 500) by restricting max amount of characters in some fields in schema. (Sandbox and Live) - concerns XSD schema
  • REST-Import-API: Contact: DELETE Contact is possible. Use the parameter assigntocontactid to assign the real estates from the old contact to the new contact. (Live) documentation
  • REST-Import-API: Response: The ScoutID (id) or ObjektID (externalId) will be shown in the response as an extra field at POST and DELETE requests. (Sandbox and Live)
  • REST-Search-API: We have secured this API with oAuth 1.0a. As from now you have to sign your Search API requests by at least 2-legged oAuth (3-legged oAuth if you use the search param "channel")

 

August 2014

  • REST-Import-API: Energy Certificate: energySourceEnev2014 has 8 new enum values by using a new query parameter. (Live) documentation
  • REST-Import-API: RealEstate: realEstateProjectId delivered in response of GETbyID Realestate request. Only supported for apartmentBuy and houseBuy. (Live) documentation
  • REST-Import-API: Energy Certificate: energySourceEnev2014 has 8 new enum value by using a new query parameter. (Sandbox) documentation
  • REST-Import-API: RealEstate: realEstateProjectId delivered in response of GETbyID Realestate request. Only supported for apartmentBuy and houseBuy. (Sandbox) documentation
  • REST-Import-API: compulsoryAuction: Less mandatory fields. Not mandatory anymore are the following fields: recordationDate, countyCourt, fileReferenceAtCountyCourt, number of folio and owner. (Live) documentation
  • REST-Import-API: compulsoryAuction: Less mandatory fields. Not mandatory anymore are the following fields: recordationDate, countyCourt, fileReferenceAtCountyCourt, number of folio and owner. (Sandbox) documentation
  • Bugfix: Generating the WADL for Import/Export API works (Live) WADL

 

June 2014

  • REST-Import-API:  Bugfix: “total floor space” is now optional for the real estate types “office” and “store“ (Live)
  • REST-Import-API:  Bugfix: wrong failure message for netFloorSpace: “MainFloorSpace” correction (Live)
  • New API: premiumPlacement (Live)  documentation
  • REST-Import-API:  Element “Courtage” has been deleted for the real estate type compulsatory aution (Zwangsversteigerung) (Live)
  • REST-Import-API:  Bugfix: “total floor space” is now optional for the real estate types “office” and “store“ (Sandbox)
  • REST-Import-API:  Bugfix: wrong failure message for netFloorSpace: “MainFloorSpace” correction (Sandbox)
  • New API: premiumPlacement (Sandbox) documentation
  • Web-Expose: Bugfix for showing € symbol, if it’s transferred correctly by REST-Import-API (Live)
  • REST-Import-API:  Element “Courtage” has been deleted for the real estate type compulsatory aution (Zwangsversteigerung) (Sandbox) documentation
  • REST-Import-API: realEstateProject: New method Realestateproject/PUTbyID. You can change your real estate project via API now. Note: All fields of a project are mandatory (Live) documentation
  • REST-Import-API: realEstateProjectEntry: You can use your own object ID (externalId) by Realestateprojectentry/POST a real estate object to a project (Live) documentation
  • REST-Import-API: realEstateProjectEntry: New method Realestateprojectentry/DELETEbyID. You can delete a real estate project entry (real estate object) from a project by using the scout ID oder your own object ID (Live) documentation
  • REST-Import-API: realEstateProject: New method Realestateproject/PUTbyID. You can change your real estate project via API now. Note: All fields of a project are mandatory (Sandbox) documentation
  • REST-Import-API: realEstateProjectEntry: You can use your own object ID (externalId) by Realestateprojectentry/POST a real estate object to a project (Sandbox) documentation
  • REST-Import-API: realEstateProjectEntry: New method Realestateprojectentry/DELETEbyID. You can delete a real estate project entry (real estate object) from a project by using the scout ID oder your own object ID (Sandbox) documentation
  • REST-Import-API: investment: priceIntervalType: At the element rentalIncomeActual und rentalIncomeTarget, additionalCosts und otherCosts since 2nd july 2014 only YEAR is allowed (Sandbox and Live) documentation
  • REST-Import-API: Energy certificate: Added new field "energyCertificateAvailability" in element "energyCertificate" with possible enum AVAILABLE, NOT_AVAILABLE_YET, NOT_REQUIRED. Please note: this field can turn on/off the EnEv Java validation (Live) - concerns XSD schema - documentation

 

May 2014

  • REST-Import-API: Energy certificate: Added new field "energyCertificateAvailability" in element "energyCertificate" with possible enum AVAILABLE, NOT_AVAILABLE_YET, NOT_REQUIRED. Please note: this field can turn on/off the EnEv Java validation (sandbox) - concerns XSD schema - documentation
  • REST-Import-API: new resource realEstateProject: GETBYID "Realestateproject" and POST/GET "Realestateprojectentry" possible. You can refer real estate objects to projects (Live) - concerns XSD schema - documentation
  • REST-Import-API: new resource realEstateProject: GETBYID "Realestateproject" and POST/GET "Realestateprojectentry" possible. You can refer real estate objects to projects (sandbox) - concerns XSD schema - documentation
  • REST-Import-API: Energy certificate: commercial real estate objects are not rejected if they contain fields with regard to the energy certificat of living real estates (Live) documentation
  • REST-Import-API: Energy certificate: commercial real estate objects are not rejected if they contain fields with regard to the energy certificat of living real estates (sandbox) documentation

 

April 2014

  • REST-Import-API: Energy certificate: Removed "old" energy fields (heatingType, firingTypes) from assistedLiving, compulsoryAuction and flatShareRoom (Live) - concerns XSD schema - documentation
  • REST-Import-API: increase max limit of Energieverbrauchskennwert (thermalCharacteristic) from 999.99 to 1,999.99 (sandbox and Live) documentation
  • REST-Import-API: validation of the energy certificate fields for all real estate types (Live) documentation
  • REST-Import-API: validation of the energy certificate fields for all real estate types. Please send only the relevant fields which you can find in the matrix (sandbox) documentation
  • REST-Import-API: Enhance amount of picture attachments to 30 (sandbox and Live) documentation
  • REST-Import-API: Energy certificate: constructionYearkUnknown persisted (Live) documentation
  • REST-Import-API: Energy certificate: Added missing new energy certificate fields to 3 real estate object types: assistedLiving, compulsoryAuction and flatShareRoom (Live) - concerns XSD schema - documentation
  • REST-Import-API: Energy certificate: Removed "old" energy fields (heatingType, firingTypes) from assistedLiving, compulsoryAuction and flatShareRoom (sandbox) - concerns XSD schema - documentation
  • REST-Import-API: Energy certificate: Added missing energy certificate fields to 3 real estate object types: assistedLiving, compulsoryAuction and flatShareRoom (sandbox) - concerns XSD schema - documentation
  • REST-Import-API: 500' bug within ressource PUBLISH is fixed (Live)
  • REST-Import-API: Changed position of the <energyCertificate> suboject in the REALESTATE ressource (Live) - concerns XSD schema
  • REST-Import-API: Energy certificate: Added all the commercial realestate types (Live) - concerns XSD schema - documentation
  • REST-Import-API: Energy certificate: Added 3 missing real estate types: compulsatory auction (Zwangsversteigerung), assistedLiving (Betreutes Wohnen), FlatShareRoom (WGs) (sandbox and Live) - concerns XSD schema - documentation
  • REST-Import-API: Energy certificate: constructionYearkUnknown persisted (sandbox) documentation

March 2014

  • REST-Import-API: 500' bug within ressource PUBLISH is fixed (sandbox)
  • REST-Import-API: Changed position of the <energyCertificate> subject in the REALESTATE ressource (sandbox)
  • REST-Import-API: Energy certificate: Added all the commercial realestate types (sandbox)
  • REST-Import-API: Added energy certificate fields for aparmentRent/Buy and houseRent/Buy (production)
  • REST-Import-API: Added energy certificate fields for aparmentRent/Buy and houseRent/Buy (sandbox)
  • REST-Import-API: CRUD operations on the ATTACHMENT resource will be available per external id, as well (production)
  • REST-Import-API: Bugfix: total floor space is not mandatory anymore for the real estate types office and store (production)

13th March 2014

  • REST-Import-API: CRUD operations on the ATTACHMENT resource will be available per external id, as well (sandbox)
  • total floor space is not mandatory anymore for the real estate types office and store (sandbox)

20th February 2014

  • REST-Import-API: Publishing a list of realestates is possible. [Documentation]

14th February 2014

  • REST-Import-API: DELETE REALESTATE available for all clients The web-service "DELETE REALESTATE" will be available for all sandbox and productional API keys in the next few days. Once the permission is set, it will be announced in the forum and on the cover page of the documentation. [Documentation] The permission will be withdrawn in case the web-service is misused, for instance for having existing real estate exposes inserted as "new".

30th January 2014

  • REST-Import-API: heatingCostsInServiceCharge has been enhanced by the value "NO".

 

28th January 2014

  • Search API: priceType is now mandatory, whenever price is set in the realEstateTypes livingrentsite and livingbuysite
  • Search API: priceType allows exactly one value for all real estate types - multi valued requests are no longer supported.
  • Search API: The pricetype rentandbuy is no longer supported for assistedliving.
  • Search API: the pricetype is no specified as a lowercase parameter name for all realestatetypes.

 

23th January 2014

We've made following changes to the Telepone/Fax/Mobile fields within CONTACT:

  • Country code (Ländervorwahl): „00“ is not allowed, it needs to be "+".
  • Area code (Regionvorwahl): if the Countrycode is "+49" than, a leading "0“ is rejected.
  • Subscriber code (Anschluss): no changes.

You may send the complete number in a single field as string. Still the restrictions apply. The one string fields are: faxNumber, phoneNumber, cellPhoneNumber.

  • For all 3 fields, only space is allowed as separator.

11th December 2013

  • Search API: Introduced the concept of flag parameters. The following parameters are now flag parameters:
    • buildingpermission
    • shorttermconstructible
    • buildingproject
    • newbuilding
    • freeofcourtageonly
  • Search API: The search apis areaDivisible criteria are derecated and will be ignored from now on. they have therefore been removed from the docs
  • Search API: Date parameters must be given in ISO 8601 standard format from now on

6th December 2013

REST-Import-API: Archived objects are handed out. Please use the following parameter: http://rest.immobilienscout24.de/restapi/api/offer/v1.0/user/testusername/realestate?archivedobjectsincluded=true

 

28th November 2013

  • Search API: The parameters smokingallowed and constructionphasetypes of the search resource do not support the value "noinformation" any more. It will be ignored from now on.
  • Search API: The Parameter priceinterval will be ignored for shorttermaccommodation querys against the search resource.
  • Search API: The parameter garagetypes of the search resource only supports the values garage and streetparking from now on. The other values are deprecated and will map to garage for backwards compatibility.

 

21st November 2013

REST-Import-API: Less mandatory fields for the real estate types investment, shorttimeaccomodation and housetype.

 

17th October 2013

REST-Import-API: We hand out state and publish channel within GETALL REALESTATE.

 

10th October 2013

  • REST-Import-API: Enhance maximum file size of videos from 10 MB to 1 GB and change in video upload process. Documentation
  • REST-Import-API: Make "house number" optional for sites (Grundstücke)

 

05th September 2013

  • REST-Import-API: GET/PUT/POST REALESTATE for objects abroad. Documentation

 

14th August 2013

  • REST-Import-API: Attribut "Mietdauer" für Büros hinzugefügt, damit können Büros in der neuen Rubrik "Büros auf Zeit" gefunden werden (new attribute "officeRentDurations" added, therewith, it's possible to publish offices in the new category "long-term office"). Documentation Available on production environment since 14th August, on sandbox approximately from 16th August.

30th July 2013

  • REST-Import-API: The order of the picture attachments to a real estate object can be changed by API. Documentation

 

22th July 2013

  • REST-Import-API: Java Client. An api consuming developer has published a Java-Signpost Java client which shows how to connect to the import-export-REST-API using signpost.

 

17th July 2013

  • Feature REST-Import-API: enable GET/PUT REALESTATE with externalId. Documentation.

 

10th July 2013

  • Change REST-Import-API: POST/PUT REALESTATE: required field constructionYear made optional for garageBuy

 

3rd July 2013

  • Feature Search-API: Added optional parameter "rent duration" to office search
  • Feature Search-API: Added optional element "rent duration" to office saveSearch

 

20th June 2013

  • Change REST-Import-API: POST/PUT REALESTATE: Street and house number in the object address are now mandatory
  • Change REST-Import-API: POST/PUT REALESTATE: NOT_APPLICABLE for HasCourtage is not allowed anymore. Therewith, HasCourtage ist mandatory.

 

13th June 2013

  • Change in Search-API: shorttermaccommodationtype: we've deleted "appartment", if you search for "appartment", it will be treated as "flat". And we've changed shorttermaccommodationtype from multiple value in single value. This change is backwards compatible.
  • Bugfix: API registration works again.
  • Change REST-Import-API: POST/PUT REALESTATE: many required fields have been set to optional. Here's the complete list:
    • energyConsumptionContainsWarmWater, thermalCharacteristic, BuildingEnergyRatingType for all relevant real estate types
    • GASTRONOMY: interiorQuality, freeFrom, constructionYear, lastRefurbishment, heatingType, numberOfFloors, additionalCosts.
    • STORE: interiorQuality, freeFrom, constructionYear, lastRefurbishment, heatingType, numberOfFloors, additionalCosts.
    • OFFICE: interiorQuality, freeFrom, constructionYear, lastRefurbishment, heatingType, numberOfFloors, additionalCosts, handicappedAccessible, cellar, flooringType
    • GARAGE: lastRefurbishment, lengthGarage, widthGarage, heightGarage, constructionYear for garageRent (for garageBuy its still mandatory like in the webinsertation)
    • INDUSTRY: interiorQuality, freeFrom, constructionYear, lastRefurbishment, heatingType, numberOfFloors, additionalCosts, flooringType.
    • TRADESITE:freeFrom, shortTermConstructible, buildingPermission, demolition, grz, gfz.
    • SPECIALPURPOSE: heatingType, freeFrom, constructionYear, interiorQuality, lastRefurbishment, numberOfFloors.

 

14th May 2013

  • Bugfix REST-Import-API: POST REALESTATE for appartment: lift=true is saved, although the client sends lift=false
  • Bugfix Search API: SHORT_TERM_ACCOMMODATION (Wohnen auf Zeit): number of rooms was missing in the result list

 

07th March 2013

  • Bugfix REST-Import-API: WAZ -> Attribute <propertyDeveloper>xxx</propertyDeveloper> was mandatory. We've deleted the attribute.
  • Bugfix REST-Import-API: POST ATTACHMENT results in an internal server error

 

27. Februar 2013

  • Feature REST-Import-API: Added two query parameter: "publishchannel" and "notinpublishchannel" to the request GET ALL REALESTATE. 
  • Feature REST-Import-API: GET ALL REALESTATE: added paging and added several attributes to the result (price, space, rooms)

20. Februar 2013

  • Bugfix REST-Import-API: API-360 PUT ATTACHMENT: wenn das Attribut <title> nicht befüllt wird, wird nun kein Dedaultwert mehr eingetragen.

13. Februar 2013

  • Bugfix REST-Import-API: Restriktionen im Schema für "attachments/attachment" und "GeoHierarchyElement/name" entfernt. Diese Attribute sind nun nicht mehr Pflicht im Schema, so dass Sie gegen das Schema validieren können, auch wenn Sie diese Attribute nicht senden
  • Bugfix REST-Import-API: Objekte könnne nicht veröffentlicht werden (POST publish-Ressource), wenn das Objektkontingent dafür nicht ausreicht. Bisher wurde dennoch eine Meldung 200 Ok ausgegeben, dass wurde nun in 412 precondition failed geändert.
  • Bugfix REST-Search-API: Man kann die Objektzahlen zu den Verfeinerungskriterien in der Ergebnisliste parameter "features=matchcount" anzeigen Doku.
  • Bugfix REST-Search-API: Parameter "nonsmoker=true/false" bei WohnenAufZeit (SHORT_TERM_ACCOMMODATION) war vertauscht.

6. Februar 2013

  • Bugfix REST-Import-API: Feldlänge für "Provisionshinweis" (Courtage note) von 200 auf 500 Zeichen erhöht.

 

23. Januar 2013

  • Feature REST-Import-API: Geohierarchy wird in GETBYID und GETALL REALESTATE ausgegeben

 

5.12 2012: Import-API-Bugfixes

  • Bugfix REST-Import-API: Paralleler Upload von Attachments für dasselbe RealEstate schlägt fehl
  • Bugfix REST-Import-API: Gründstücke (livingRent/Buy tradeSite) > siteRecommendedUseType sollte childs erlauben
  • Bugfix REST-Import-API: Deposit in Offer RealEstate should have maxInclusive

 

28.11: Import-API-Bugfixes

  • Bugfix REST-Import-API: FreeFrom in RealEstate Insertion hat keine Einschrünkung auf 50 Zeichen wie in der Web
  • Bugfix REST-Import-API: REALESTATE POST und PUT" Floor" akzeptiert negative zahlen
  • Bugfix REST-Import-API: real estate > house rent > price sollte nicht mandatorisch sein (da hier nur baserent benötigt)
  • Bugfix REST-Import-API: get realestate id = alphanumerisch wirft 500er
  • Bugfix REST-Import-API: livingRent/Buy or tradesite > pflichtfeld <leaseInterval>WEEK</leaseInterval> unlogisch
  • Bugfix REST-Import-API: übergabe von feld <assistedLiving>true</assistedLiving> sollte nicht mehr möglich sein

 

21.11.2012: Import-API-Bugfixes

  • Bugfix REST-Import-API: GET realEstate?publishchannel=10000 führt zu "mapper not implemented"-Fehlermeldung
  • Bugfix REST-Import-API: POST/PUT REALESTATE mit fremder oder nicht existierender ContactID resultiert in statuscode 403 bzw 404 (anstatt 412)
  • Bugfix REST-Import-API: PUT auf HP published REALESTATE deaktiviert dieses

 

14.11.2012: Search-API-Bugfix

Bugfix Search API: Bilder URLs mit leerem Inhalt werden ausgeliefert

 

7.11.2012: Feature und Bugfix in Import-API

  • Feature REST-Import-API: beim Webservice PUBLISHCHANNEL "User" in der URI mit aufnehmen und anstelle vom Username auch "me" erlauben
  • Bugfix REST-Import-API: PUT auf veröffentlichtes RealEstate erzeugt Hibernate 500er

 

24.10.2012: Bugfix Import-API

Bugfix REST-Import-API: Zugriff auch auf Angebote via "me" und nicht nur via Username

 

17.10.2012: Search-API: Trefferzahl zu den Verfeinerungskriterien in der result list ausgeben

Feature REST-Search-API: Trefferzahl zu den Verfeinerungskriterien in der result list ausgeben

 

03.10.2012: Bugfixes und ein Feature für die Suche- und Import-API

  • Bugfix REST-Import-API: Pricetype doesn't support multiple values
  • Bugfix Search-API: Search query parameter rented ignores null
  • Feature REST-Import-API: CONTACT per foreign-id (CRUD)

 

19.09.2012: Immobilientyp Zwangsversteigerung in REST-Import-API

Feature REST-Import-API: Immobilientyp Zwangsversteigerung in REST-Import-API aufgenommen

 

12.9.2012: Bugfix oAuth und Feature Import-API

  • Bugfix oAuth: Encodierte Prozentzeichen kommen über den Apache falsch im Tomcat an, so dass die Oauth-Signature nicht mehr stimmt
  • Feature REST-Import-API: Immobilientyp Typenhaus in REST-Import-API aufgenommen

 

05.09.2012: 11 Immotypen in Import-API aufgenommen

  • Feature REST-Import-API: Immobilientypen Anlage, Wohnen auf Zeit, alle 6 Gewerbeimmobilientypen und alle 3 Grundstücksimmobilientypen in REST-Import-API aufgenommen

 

29.08.2012: Immobilientyp Wohnung Kauf in REST-Import-API aufgenommen

Feature REST-Import-API: Immobilientyp Wohnung Kauf in REST-Import-API aufgenommen

 

15.08.2012: 11 Immotypen in Import-API aufgenommen

  • Bugfix REST-Search-API: Expose request broken
  • Feature REST-Import-API: Immobilientypen Haus Miete und Wohnung Miete sowie Betreutes Wohnen und Altenpflege in REST-Import-API aufgenommen

 

02.08.2012: Suchfilter "Neubau" (newbuilding)

Für 4 Immobilientypen (Wohnung Miete/Kauf und Haus Miete/Kauf) kann nach "neubau" gefiltert werden. Dabei werden Objekte dessen Baujahr < 3 Jahre sowie Neubauprojekte, berücksichtigt. Doku

 

25. Juli 2012: Search-API: es werden Objektzahlen zu den Regionen ausgegeben

Wir erweitern die Search-API kontinuierlich: seite heute ist der geo-statistics-Webservice live. Dieser zeigt die Objektzahlen zu den Regionen an, wenn man die Suche über die Geohierarchie ausführt. z.B. Berlin: Prenzlauer Berg (145), Friedrichshain (1403), Mitte (123). Doku

 

11. Juli 2012: zwei neue Suchfilter, Ergebnisliste-Eintrag enthält Veröffentlichungsdatum

1. Suchparameter publishedafter

Speziell für mobile Clients haben wir den Featurewunsch “ich möchte wissen, welche Objekte seit Datum X (z.B. seit der letzte lokal gespeicherte Suche) veröffentlicht wurden um diese in der Ergebnisliste entsprechend als “NEU” zu kennzeichnen”, umgesetzt.

Dazu wurde für die region search und die radius search ein neuer Suchparameter eingeführt: publishedafter. Das Suchergebnis wird dabei nicht gefiltert, sondern die Objekte bekommen ein weiteres Attribut. Doku

Request: http://rest.immobilienscout24.de/restapi/api/search/v1.0/search/region?realestatetype=apartmentrent&geocodes=1276&publishedafter=2012-06-01T00:00:00

Response: Die Ergebnisliste-Einträge enthalten sowohl ein Booleanwert als auch das publishDate des Objektes, wenn der Suchparameter “publishedafter” angegeben wurde <entry> <publishDate>05.06.2012<\publishDate> <publishedAfter date=”01.06.2012″> true <\publishedAfter> …. <\entry>

 

2. Suchparameter “firstactivation

Du möchtest nur die Objekte bekommen, die seit Tag X veröffentlicht wurden? z.B. um in einer Übersicht mit letzten – und gespeicherten- Suchen anzeigen zu können, wie viele Objekte neu hinzugekommen sind? Dazu haben wir den Suchparameter “firstactivation” eingeführt, der nur die Objekte liefert, die nach Tag X veröffentlicht wurden. Doku

Request: http://rest.immobilienscout24.de/restapi/api/search/v1.0/search/region?realestatetype=apartmentrent&geocodes=1276&firstactivation=2012-06-01T00:00:00

 

3. Veröffentlichungsdatum (“publishDate”) in Ergebnisliste-Einträge mitausgeben

Denn das Creationdate sagt nur aus, wann ein Objekt in der ImmobilienScout24-Datenbank angelegt wurde, nicht wann es veröffentlicht wurde. Das Creationdate wird aus Kompabilitätsgründen beibehalten.

<resultlistEntry publishDate=”2012-06-29T12:05:16.000+02:00″ creation=”2012-06-29T12:05:03.000+02:00″ modification=”2012-07-01T20:54:35.000+02:00″ id=”61971321″ xlink:href=”http://rest.immobilienscout24.de/restapi/api/search/v1.0/expose/61971321″>

 

27. Juni: API-Search-Fields werden auch im Ergebnislisteneintrag und Expose ausgegeben

Die API-Suchefelder sind nicht nur als Suchparameter vorhanden, sondern werden nun auch im resultlistentry und expose ausgegeben. Damit ist es z.B möglich eine Exposeliste nach Kriterien zu erstellen, die IS24 nicht als Expose-Feld anbietet, stattdessen setzt der Immobilienanbieter die benötigte Werte in den API-Suchefelder (wie z.B. "kamin", "niedrigenergiehaus", "pool", "sauna" usw.)

 

19. Juni 2012: Suche nach channel={groupid} ist nun ohne Berechtigung möglich

Die group-id sollte der Auftraggeber kennen bzw. bei seinen Kundenbetreuer von Immobilienscout24 anfragen können. Doku

 

4. April: Suchfilter "Provisionsfrei" für alle Immotypen, Bugfixes und der letzte Immotyp "Zwangsversteigerung"

  • Bugfix: bei deaktiven Exposes wird “404 NOT FOUND” statt “403 ERROR_COMMON_ACCESS_DENIED” ausgegeben
  • Bei Nicht-Verfügbarkeit der REST-API geben wir nun “503 Service unavailable” aus.
  • Downtime-Releases bei der auch die REST-API nicht verfügbar ist gibt es 1x/Monat, in der Nacht von Mittwoch zu Donnerstag zwischen 01-04.00 Uhr
  • “Provisionsfrei” (freeofcourtageonly) ist verfügbar für alle andere Immotypen (sowohl für die Suche als auch für Suche speichern), bei der man nach diesem Parameter suchen kann

 

24. Februar: zwei weitere Immobilientypen

  • Drei neue Immobilientypen stehen zur Verfügung: assisted living (Betreutes wohnen) und senior care (Altenpflege).
  • Suche nach Auslandsimmobilien ist da.
  • Suchparameter “freeofcourtageonly” (Provisionsfrei): es ist nun möglich eine Suche mit diesen Parameter zu speichern für diese Immotypen:
  • appartment rent&buy,
  • house rent&buy and
  • site rent&buy