- 21 Feb 2025
- 5 Minutes to read
- Print
- DarkLight
Get buildings filtered and paged
- Updated on 21 Feb 2025
- 5 Minutes to read
- Print
- DarkLight
[PREVIEW] Get a paged list of existing buildings, optionally filtered to the given parameters.
Description
Retrieve a paged list of existing buildings, optionally filtered to the given parameters. The Bloxs real estate objects-api offers 2 options to get buildings filtered and paged. One is through the POST option, and as an alternative there is a GET operation available. The functional difference is that the POST option offers the ability to sort the results. Furthermore, the POST includes the parameters in the body whereas the GET includes them in the url.
Either reference or externalIdentifier must have a value. Please note that if both identifiers are given, both must match; otherwise, an error message will be generated. It is recommended that the user utilizes only one identifier, with a preference for the reference.
A building is a standalone entity. It refers to a terraced house or an entire building that is not divided into multiple parts. A building is a rentable unit. If it contains multiple rental units, it is no longer considered a single building. A building can be included in a rental contract.
Use Case
The Bloxs user has an external App connected to Bloxs. Through this operation the user can display a paged list of buildings & the related information. This operation can be used if the user wants to display multiple buildings rather than just a specific one. If the user wants to display a single building the preference is to use the GET (buildings) operation.
Field | Description |
---|---|
paging.pageSize | The maximum number of pages to be returned per request. The default number is 100 and the maximum is 1.000. If more results are returned than specified in the PageSize, the remaining pages are dropped based on the reference (number). |
paging.pageNumber | This allows the requesting party to specify which of the pages they want to receive. |
sorting.columnName | The data field based on which sorting will be applied. For example, if the user wants to sort the results based on ascending name, the value 'name' should be given here. |
sorting.order | Based on this value, the property defined in 'columnName' will either be sorted ascending (a-z) or descending (z-a). |
name | The custom name assigned to the object. This is used for reporting and to distinguish the object when the address alone is insufficient. In the case of room rentals, this would be the address + room number. This name can also be displayed on invoices and bills. |
reference | The relationship number within Bloxs. This is unique (per client specific environment) for all objects. The relationship number is generated by the Bloxs system. |
externalIdentifier | The unique identifier within the system of the requesting party. This identifier is not generated by the Bloxs system. |
ownerReference | Property owner. This field is used to link the property to its owner. Since a property must have an owner, this field is mandatory. It is part of the contracts triangle of properties, owners, and tenants. The OwnerReference corresponds to the 'Reference' in the Relations. This unique ID is generated by the Bloxs portal and should not be confused with the external identifier. A property can have only one owner. |
estateAgentReference | Real estate agent for the property This field links the property to a real estate agent. It must be an existing agent who has been previously added either through the Bloxs application or via the API. The estateAgentReference corresponds to the 'Reference' previously assigned to the real estate agent. This unique ID is generated by the Bloxs application and should not be confused with the external identifier. A property can have only one real estate agent. |
addressStreetAndHousenumber | Street and house number of the object. |
addressPostalCode | Postal Code of the object. |
addressCity | City in which the object is located. |
addressCountryISOCode | Country in which the object is located. ISO language code. Use the 2-letter code from the ISO 639-1 Code list. |
rawFloorArea.from | Gross Floor Area The total measured floor area according to the NEN2580 standards. Decimals are separated with a period (.). The minimum raw floor area that must be used for the selection. |
rawFloorArea.to | Gross Floor Area The total measured floor area according to the NEN2580 standards. Decimals are separated with a period (.). The maximum raw floor area that must be used for the selection. |
rentableFloorArea.from | Rentable Floor Area Rentable floor area according to the NEN2580 standards. Decimals are separated with a period (.). The minimum rentable floor area that must be used for the selection. |
rentableFloorArea.to | Rentable Floor Area Rentable floor area according to the NEN2580 standards. Decimals are separated with a period (.). The maximum rentable floor area that must be used for the selection. |
usableFloorArea.from | Usable Floor Area The surface of the floor that can actually be used. The minimum usable floor area that must be used for the selection. |
usableFloorArea.to | The maximum usable floor area that must be used for the selection. |
underManagementSince.from | From this date, the user has become the manager of the object. The date is initially entered and remains unchanged until the sale/termination of management. |
underManagementSince.to | The end date from which the user is no longer the manager of the object. |
salesDate.from | The starting date on which the object was sold or is no longer under management. |
salesDate.to | The end date on which the object was sold or is no longer under management. |
LastModified.from | The starting date on which a building was last modified |
LastModified.to | The end date on which a building was last modified. |
Please enter a valid token
0 = Ascending
1 = Descending
OK
0 = Ascending
1 = Descending