- 07 Feb 2025
- 5 Minutes to read
- Print
- DarkLight
Insert a section
- Updated on 07 Feb 2025
- 5 Minutes to read
- Print
- DarkLight
[PREVIEW] Insert a new section.
Description
Insert (add) an section to your existing real estate objects.
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.
The 200 response contains a field named 'reference'. It is important to save this value since it is used as an identifier for all the other operations to recognise this specific entity.
Use Case
The user wants to add a section from a third party system to the Bloxs application. Consequently the section can be selected in the Bloxs application for other processes such as contracting.
Request fields
The request contains the following fields:
Field | Description |
---|---|
externalIdentifier | The unique identifier within the system of the requesting party. This identifier is not generated by the Bloxs system. |
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. |
categoryName | The name of the category. The enumeration can be set by the user in the admin module. In the administration, there is already a default list created by Bloxs, which can be modified by the user. |
extraRelations | Via this field any existing relation (Person, organisation, supplier, Owner or Estate Agent) can be linked to this object. For example, if a certain person is responsible for the maintenance, this method can be used to link this person to the object. Note that only existing relations can be linked. New relations should be entered through the relations-api. |
extraRelations.extraRelationTypeName | The relation type of the existing relation that should be linked to this object. This is a separate field from the 'RelationTypeName' in the relations-api. The extraRelationTypeName refers to the relation type specifically assigned to the this object. For example, a person has the relationTypeName maintenance assigned. However, for this specific object the person performs the role of cleaner rather than maintenance. Through the field extraRelationTypeName the role of cleaner can be assigned. The enumeration can be set by the user in the admin module. In the administration, there is already a default list created by Bloxs, which can be modified by the user. In order to retrieve the available list of relation types, the following GET can be used: |
extraRelations.reference | The reference of the existing relation that should be linked to this object. The reference should be identical to the reference such as registered in the Bloxs application. |
remarks | Comments for free text. Anything that cannot be entered in the other fields can be entered here. It is important not to enter sensitive information here (passwords, personal data, etc.). |
underManagementSince | 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. |
complexReference | 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. |
address | The address of the object. Please note: A change in the address of a section will not automatically update the address of the associated complex or building. If the address of the associated complex or building also changes, this change must be submitted separately via the relevant API. |
street | Address of the object. |
housenumber | Housenumber of the unit. This field could also be used to enter the room number. |
postalCode | Postal code of the object. |
city | The place (city/town) in which the object is situated. |
countryISOCode | ISO country code. Use the 2-letter code from the ISO 639-1 Code list. |
Response fields
The response contains the fields in the table below.
Field | Description |
---|---|
displayName | A combination of the 'address' & the 'name' of the object. |
salesDate | This is the date on which the object was sold or is no longer under management. Entering this date will result in the object being archived, and it will no longer be selectable in lists, etc. This date cannot be filled in if the object still has active contracts. |
lastModified | Timestamp of the last modification within Bloxs (determined by Bloxs). |
OwnerReference | Property owner. This field is used to link the property to its owner. It is part of the contracts triangle of properties, owners, and tenants. The OwnerReference corresponds to the 'Reference' in the Relations. API. 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. |
totalRawFloorArea | Gross Floor Area. The total measured floor area of all rentable units contained in the complex according to the NEN2580 standards. Decimals are separated with a period (.). |
totalRentableFloorArea | Rentable Floor Area. Rentable floor area of all rentable units contained in the complex according to the NEN2580 standards. Decimals are separated with a period (.) |
totalUsableFloorArea | The total actual usable floor area of all rentable units contained in the complex. |
Please enter a valid token
The section was created
The section data has validation issues