---
title: "Get service tickets filtered and paged"
slug: "preview-get-service-tickets-filtered-and-paged-1"
updated: 2026-02-10T13:08:49Z
published: 2026-02-10T13:08:49Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://www.bloxs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get service tickets filtered and paged

Post/api/v1/maintenance/servicetickets/filter

Get a paged list of existing service tickets, optionally filtered to the given parameters.

		
			

**Description**

Retrieve a paged list of existing service tickets, optionally filtered to the given parameters.

**Use Case**

The Bloxs user has an external App connected to Bloxs and wants to display all the service tickets that are currently 'Active' and have the priority 'high'. By entering these two parameters in this endpoint the user can retrieve all service tickets that meets these parameters, and display them in the App.

**Request****fields**

The request contains the following fields:

| Field | Description |
| --- | --- |
| 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). |
| pageNumber | This allows the requesting party to specify which of the pages they want to receive. |
| 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. |
| order | Based on this value, the property defined in 'columnName' will either be sorted ascending (a-z) or descending (z-a). |
| reference | The unique identifier for this service ticket within Bloxs. This is unique (per client specific environment) for all service tickets. This identifier 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. |
| reportingDate | The date on which the service ticket was created. This value is not automatically generated by the Bloxs system. If this field is left empty, the request will be invalid. |
| stateName | Name of the current status of the service ticket. Bloxs provides a standard list with options, however the user can modify the list with options in the admin module. In order to retrieve the full list of currently available status names, the following endpoint can be used: [GET states](/v1-api/apidocs/preview-get-all-service-ticket-states). |
| priority | Priority level of the report. This is based on a fixed list predefined by Bloxs, and cannot be modified by users. Each priority level is linked to reminder settings, which trigger tasks or emails at a defined frequency. |
| problemCategoryName | Pertains to the problem category to which the service ticket belongs. This is a standard list predefined by Bloxs, that indicates the category of the issue, such as electrical, windows, etc. In order to retrieve the full list of available category names, the following endpoint can be used: [GET problem categories](/v1-api/apidocs/preview-get-all-service-ticket-problem-categories). |
| realEstateObjectReference | This pertains to the reference of the real estate object to which the service ticket applies. Please note, a reference relating to a real estate object must be included here. |
| reporterReference | This reference refers to the person who should be contacted with any communication regarding the service ticket. Please note that a reference of a relation (see relations API) must be included here and the contact has to exist within Bloxs. |
| tenantReference | The tenant reference. This will automatically be populated based on the date the service ticket was submitted and the registered tenant of the property at that time. |
| supplierReference | This reference refers to the supplier. Please note that a relation reference (see relations API) must be included here and the supplier has to exist within Bloxs. |

		
		
SecurityHTTPType Bearer

Please enter a valid token

Body parameters<select class='api-response-data' aria-label='Media type'><option value='2e065ec0-d70d-4bdf-899a-75b0766339fd'>application/json</option>
</select>Expand Allobject  pagingobject (PagingInfo)  pageSizeinteger  (int32)   | null  Minimum1Maximum1000
pageNumberinteger  (int32)   | null  Minimum1Maximum9999

sortingobject (SortingInfo)  columnNamestring   | null  
orderinteger  (int32)    Valid values[
  0,
  1
]

filterobject (ServiceTicketSearchRequestFilter)  referencestring   | null  
externalIdentifierstring   | null  
reportingDateobject (CompareFilterModelDateTime)  fromstring  (date-time)   | null  
tostring  (date-time)   | null  

stateNamestring   | null  
priorityinteger  (int32)   | null  Valid values[
  1,
  2,
  3
]
problemCategoryNamestring   | null  
realEstateObjectReferencestring   | null  
reporterReferencestring   | null  
tenantReferencestring   | null  
supplierReferencestring   | null  

Responses200

OK

<select class='api-response-data' aria-label='Media type'><option value='c67370c6-2ca3-4ac0-8090-ba688162bc9d'>application/json</option>
</select>Expand Allobject  pagingobject (PagingInfo)  pageSizeinteger  (int32)   | null  Minimum1Maximum1000
pageNumberinteger  (int32)   | null  Minimum1Maximum9999

sortingobject (SortingInfo)  columnNamestring   | null  
orderinteger  (int32)    Valid values[
  0,
  1
]

serviceTickets Array of object (ServiceTicketSearchResultFilter)  | null  object  referencestring   | null  
externalIdentifierstring   | null  
reportingDatestring  (date-time)    
stateNamestring   | null  
priorityinteger  (int32)    Valid values[
  1,
  2,
  3
]
problemCategoryNamestring   | null  
realEstateObjectReferencestring   | null  
reporterReferencestring   | null  
tenantReferencestring   | null  
supplierReferencestring   | null
