Accruent Siterra 26.5 Release Notes

API

Authorized API users can now create events using the Events POST endpoint. This applies when the event type uses an auto-create library template with at least one document container.

The API creates the event and creates all associated libraries without returning a service resolution error.

Example endpoint

POST /apis/sit/events/v1/Events

Example payload

{
    "TypeId": 713065555,
    "StatusId": 1362120,
    "PropertyId": 1056655,
    "ResponsibleGroupId": 1000047
}

This requires feature toggle SP_38274 to be enabled. Contact Accruent Support if you need assistance with this setting.

The Assets API now supports complex OData $filter expressions using multiple OR conditions.

GET /assets/v1/Assets

The AssignResponsibilities REST API now enforces specific permission checks for non-admin users.

Example endpoint

POST /projects/v1/assignresponsibilities

The Incidents REST API now enforces specific permission checks for GET, POST, PATCH, and DELETE operations.

Example endpoint

GET /events/v1/incidents

API

The Libraries GET endpoint now enforces role-based access in line with the user interface. Authorized API users receive a 200 response with only the libraries they are authorized to view. Users without enough permissions receive standard 401 or 403 error responses without exposing library data. The existing endpoint URL remains so that current integrations do not need any changes.

Example endpoint

GET /documents/v1/libraries

API

The Libraries POST endpoint now enforces role-based access in line with the user interface. Authorized API users can now create document libraries.

Example endpoint

POST /documents/v1/libraries

Example payload (simplified):

{ 
    \"name\": \"Project Library\",
    \"description\": \"Library for project documents\"
}

API

The Libraries PATCH endpoint now enforces role-based access in line with the user interface. Authorized API users can now update document libraries they’re permitted to manage. The endpoint responds with standard 401 or 403 responses for users without enough permissions.

Example endpoint

PATCH /documents/v1/libraries({libraryID})

Example payload (simplified):

{ 
    \"description\": \"Updated library description\"
}

API

The UploadToObjectLibrary POST endpoint now enforces role-based access in line with the user interface. Authorized API users can now upload documents to an object library. The endpoint responds with standard 401 or 403 responses for users without enough permissions.

Example endpoint

POST /documents/v1/UploadToObjectLibrary

Use this endpoint to attach files to the object library by specifying the target object and library in the request. This makes it easier to automate document management workflows and keep object-related documents centralized and up to date.

Example request

POST {{fullyQualifiedDomainName}}{{baseApiPath}}/documents/v1/UploadToObjectLibrary
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary123
------WebKitFormBoundary123
Content-Disposition: form-data; name="libraryId"
12345
------WebKitFormBoundary123
Content-Disposition: form-data; name="fileName"
signed-lease-agreement.pdf
------WebKitFormBoundary123
Content-Disposition: form-data; name="file"; filename="signed-lease-agreement.pdf"
Content-Type: application/pdf
<binary file content here>
------WebKitFormBoundary123-

API

The LibraryTemplates GET endpoint now enforces role-based access in line with the user interface. Authorized API users receive a 200 response with only the library templates they are authorized to view. Users without enough permissions receive standard 401 or 403 error responses without exposing library template data.

Example endpoint

GET /documents/v1/libraryTemplates

API

The Sections GET endpoint now enforces role-based access in line with the user interface. Authorized API users receive a 200 response with only the sections they are authorized to view. Users without enough permissions receive standard 401 or 403 error responses without exposing section data.

Example endpoint

GET /documents/v1/sections

API

Authorized (non-admin) API users can now call the Documents Categories GET endpoint when their assigned groups and roles allow it. This endpoint now enforces access rights and permissions based on the user’s group and role assignments.

Example endpoint

GET /api/v1/documents/categories

You can now edit and save Hub Extended Attributes in the Subtask Extension flow. The system retains updates after you save and reload the results.

Leases

Siterra now calculates semi-annual incremental lease payments for multiple escalations. The system applies accurate amounts even if payment periods do not align with calendar dates. This helps you avoid small errors and reduces manual credits. System-calculated values now more closely match landlord invoices and tax documentation.

Payment line generation now calculates the number of payment lines for mid-month payment date scenarios, ensuring the system generates the final payment line and allocates amounts to the correct lines.

Leases – Escalations

Non-admin users with the new Bulk Delete permission can now delete orphaned payment escalations when shortening a payment header end date. An authorization error no longer appears. Administrators can assign this permission under Global Permissions for Roles > Escalations.

When you change the lease status to Terminated, Siterra now triggers the termination workflow if the core form feature toggle is enabled.

Leases

When you update the payee allocation on a parent payment, the updated payee now cascades to linked recurring calculated tax payment allocations and planned tax lines without needing manual updates or approvals.

Reports

The Vendor Contact Details report now matches the information on the Vendor page. The report no longer shows old data for blank email fields. It also displays long email addresses in full.

Save

The confirmation message that displays when you save changes and there are no changes to save now reads No changes to save, which is clearer and more concise.

Tasks

Siterra now displays a clear, actionable message when you change the Forecast Date of a task where that date is calculated from subtask durations. The message explains that you cannot edit Forecast Date. To change it, update the dates or durations of the relevant subtasks.