Contents x
    Get sections filtered and paged
    • 07 Feb 2025
    • 4 Minutes to read
    • Print
    • Dark
      Light
    Contents

    Get sections filtered and paged

    • Updated on 07 Feb 2025
    • 4 Minutes to read
    • Print
    • Dark
      Light
    Article summary

    Post
    /api/v1/realestateobjects/sections/filter

    [PREVIEW] Get a paged list of existing sections, optionally filtered to the given parameters.

    Description

    Retrieve a paged list of existing sections, optionally filtered to the given parameters. The Bloxs real estate objects-api offers 2 options to get sections 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.

    A section refers to sections of a building. Example: A complex containing a building with a shop on the ground floor and three apartments above it. This is a combination of commercial real estate and residential living. It is crucial to set this up correctly as it forms the foundation of the object structure in Bloxs: proper cost allocation, reporting purposes, assignment of a 'concierge,' and creation of (service) notifications.

    Use Case

    The Bloxs user has an external App connected to Bloxs. Through this operation the user can display a paged list of sections & the related information. This operation can be used if the user wants to display multiple sections rather than just a specific one. If the user wants to display a single section the preference is to use the GET (sections) operation.  

    FieldDescription
    paging.pageSizeThe 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.pageNumberThis allows the requesting party to specify which of the pages they want to receive.
    sorting.columnNameThe 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.orderBased on this value, the property defined in 'columnName' will either be sorted ascending (a-z) or descending (z-a).
    nameThe 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.
    referenceThe relationship number within Bloxs. This is unique (per client specific environment) for all objects. The relationship number is generated by the Bloxs system.
    externalIdentifierThe unique identifier within the system of the requesting party. This identifier is not generated by the Bloxs system.
    complexReference

    Complex associated with the property

    This field links the property to a complex. It must be a complex which has been previously added either through the Bloxs application or via the API. The complexReference corresponds to the 'Reference' previously assigned to the complex. This unique ID is generated by the Bloxs application and should not be confused with the external identifier. A property can only be part of one complex.

    ownerReferenceProperty 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.

    addressStreetAndHousenumberStreet and house number of the object. 
    addressPostalCodePostal Code of the object.
    addressCityCity in which the object is located.
    addressCountryISOCodeCountry is which the object is located.
    ISO language code. Use the 2-letter code from the ISO 639-1 Code list.
    underManagementSince.fromFrom 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.toThe end date from which the user is no longer the manager of the object.
    salesDate.fromThe starting date on which the object was sold or is no longer under management.
    salesDate.toThe end date on which the object was sold or is no longer under management.
    LastModified.fromThe starting date on which a building was last modified
    LastModified.toThe end date on which a building was last modified.
    Security
    HTTP
    Type Bearer

    Please enter a valid token

    Body parameters
    Expand All
    object
    paging
    object (PagingInfo)
    pageSize
    integer (int32) | null
    Minimum1
    Maximum1000
    pageNumber
    integer (int32) | null
    Minimum1
    Maximum9999
    sorting
    object (SortingInfo)
    columnName
    string | null
    order
    integer (int32)

    0 = Ascending

    1 = Descending

    Valid values[ 0, 1 ]
    filter
    object (SectionSearchRequestFilter)
    name
    string | null
    reference
    string | null
    externalIdentifier
    string | null
    complexReference
    string | null
    ownerReference
    string | null
    estateAgentReference
    string | null
    addressStreetAndHouseNumber
    string | null
    addressPostalCode
    string | null
    addressCity
    string | null
    addressCountryISOCode
    string | null
    underManagementSince
    object (CompareFilterModelDateTime)
    from
    string (date-time) | null
    to
    string (date-time) | null
    salesDate
    object (CompareFilterModelDateTime)
    from
    string (date-time) | null
    to
    string (date-time) | null
    lastModified
    object (CompareFilterModelDateTime)
    from
    string (date-time) | null
    to
    string (date-time) | null
    Responses
    200

    OK

    Expand All
    object
    paging
    object (PagingInfo)
    pageSize
    integer (int32) | null
    Minimum1
    Maximum1000
    pageNumber
    integer (int32) | null
    Minimum1
    Maximum9999
    sorting
    object (SortingInfo)
    columnName
    string | null
    order
    integer (int32)

    0 = Ascending

    1 = Descending

    Valid values[ 0, 1 ]
    sections
    Array of object (SectionSearchResultFilter) | null
    object
    name
    string | null
    reference
    string | null
    externalIdentifier
    string | null
    complexReference
    string | null
    addressStreetAndHouseNumber
    string | null
    addressPostalCode
    string | null
    addressCity
    string | null
    addressCountryISOCode
    string | null
    rawFloorArea
    number (double) | null
    rentableFloorArea
    number (double) | null
    usableFloorArea
    number (double) | null
    underManagementSince
    string (date-time) | null
    salesDate
    string (date-time) | null
    lastModified
    string (date-time)
    What's Next