> ## Documentation Index > Fetch the complete documentation index at: https://docs.aseeflow.org/llms.txt > Use this file to discover all available pages before exploring further. # Execute Filter List (POST) > Executes the saved query of the filter by id and returns the result list. This method is slightly more powerful then the [Get Execute FilterList](https://docs.aseeflow.org/reference/rest/filter/get-filters/) method because it allows to extend the saved query of the filter. ## OpenAPI ````yaml /reference/rest/openapi-1.0.json post /filter/{id}/list openapi: 3.0.2 info: title: ASEE Flow Platform REST API description: OpenApi Spec for ASEE Flow Platform REST API. version: 1.0.0 license: name: Apache License 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: http://{host}:{port}/{contextPath} description: The API server for the default process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest - url: http://{host}:{port}/{contextPath}/engine/{engineName} description: The API server for a named process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest engineName: default: default - url: '{url}' description: The API server with a custom url variables: url: default: '' security: - basicAuth: [] tags: - name: Authorization - name: Batch - name: Condition - name: Decision Definition - name: Decision Requirements Definition - name: Deployment - name: Engine - name: Event Subscription - name: Execution - name: External Task - name: Filter - name: Group - name: Historic Activity Instance - name: Historic Batch - name: Historic Decision Definition - name: Historic Decision Instance - name: Historic Decision Requirements Definition - name: Historic Detail - name: Historic External Task Log - name: Historic Identity Link Log - name: Historic Incident - name: Historic Job Log - name: Historic Process Definition - name: Historic Process Instance - name: Historic Task Instance - name: Historic User Operation Log - name: Historic Variable Instance - name: History Cleanup - name: Identity - name: Incident - name: Job - name: Job Definition - name: Message - name: Metrics - name: Migration - name: Modification - name: Process Definition - name: Process Instance - name: Signal - name: Schema Log - name: Task - name: Task Attachment - name: Task Comment - name: Task Identity Link - name: Task Local Variable - name: Task Variable - name: Telemetry - name: Tenant - name: User - name: Variable Instance - name: Version externalDocs: description: Find out more about ASEE Flow Rest API url: https://docs.aseeflow.org/reference/rest/overview/ paths: /filter/{id}/list: post: tags: - Filter summary: Execute Filter List (POST) description: >- Executes the saved query of the filter by id and returns the result list. This method is slightly more powerful then the [Get Execute FilterList](https://docs.aseeflow.org/reference/rest/filter/get-filters/) method because it allows to extend the saved query of the filter. operationId: postExecuteFilterList parameters: - name: id in: path schema: type: string required: true description: The id of the filter to execute. - name: firstResult in: query schema: type: integer description: >- Pagination of results. Specifies the index of the first result to return. - name: maxResults in: query schema: type: integer description: >- Pagination of results. Specifies the maximum number of results to return. Will return less results if there are no more results left. requestBody: description: >- A JSON object which corresponds to the type of the saved query of the filter, i.e., if the resource type of the filter is Task the body should form a valid task query corresponding to the Task resource. content: application/json: schema: type: object examples: example-1: summary: request description: >- POST `/filter/aTaskFilterId/list/?firstResult=0&maxResults=2`. **Note**: The examples show a task filter. So the request body corresponds to a task query. For other resource types the request body will differ. value: assignee: jonny1 taskDefinitionKey: aTaskKey responses: '200': content: application/json: schema: type: array items: type: object examples: example-1: summary: request description: >- POST `/filter/aTaskFilterId/list/?firstResult=0&maxResults=2`. **Note**: The examples show the result of a task filter. So the response corresponds to a task, but for other filters the response format will differ. value: - assignee: jonny1 caseDefinitionId: null caseExecutionId: null caseInstanceId: null created: 2014-09-15T15:45:48.000+0200 delegationState: null description: null due: null executionId: aExecutionId followUp: null formKey: null lastUpdated: 2014-09-15T15:45:48.000+0200 id: aTaskId name: Task 2 owner: null parentTaskId: null priority: 50 processDefinitionId: aProcessId processInstanceId: aProcessInstanceId suspended: false taskDefinitionKey: aTaskKey description: >- Request successful. A JSON array containing JSON objects corresponding to the matching entity interface in the engine. This depends on the saved query in the filter. Therefore it is not possible to specify a generic result format, i.e., if the resource type of the filter is Task the result will correspond to the Task interface in the engine. '400': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: > The extending query was invalid. See the [Introduction](https://docs.aseeflow.org/reference/rest/overview/#error-handling) for the error response format. '403': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: > The authenticated user is unauthorized to read this filter. See the [Introduction](https://docs.aseeflow.org/reference/rest/overview/#error-handling) for the error response format. '404': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: > Filter with given id does not exist. See the [Introduction](https://docs.aseeflow.org/reference/rest/overview/#error-handling) for the error response format. components: schemas: ExceptionDto: title: ExceptionDto type: object properties: type: type: string nullable: true description: An exception class indicating the occurred error. message: type: string nullable: true description: A detailed message of the error. code: type: number description: >- The code allows your client application to identify the error in an automated fashion. You can look up the meaning of all built-in codes and learn how to add custom codes in the [User Guide](https://docs.aseeflow.org/user-guide/process-engine/error-handling/#exception-codes). securitySchemes: basicAuth: type: http scheme: basic ````