> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/api-documentation/api-reference/api--response-center/types/inputs/get-incident-remediation-page-input.md).

# getIncidentRemediationPageInput

Selects the section, filters, search, sort and page of the Remediation tab rows to return.

### Examples

```graphql
input GetIncidentRemediationPageInput {
  section: RemediationSection
  itemLimit: Int
  cursor: String
  search: String
  conditionalFilters: [IncidentConditionalFilterInput!]
  sortBy: RemediationSortField
  sortOrder: SortOrder
}
```

### Fields

| Field                                                                                                                                                                                     | Description                                                                                                                                                                                                                                                                                                                                                                                                                                    | Supported fields                                                                                                                                                                                                                                                 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| section [`RemediationSection`](https://docs.ox.security/api-documentation/api-reference/api--response-center/types/enums/remediation-section.md)                                          | Limits the response to one section, for loading further pages of that section. When absent, every section is returned.                                                                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                  |
| itemLimit `Int`                                                                                                                                                                           | The maximum number of rows returned per section, at least 1. With section, at most 200. Without section, at most 50; a larger value is lowered to the maximum.                                                                                                                                                                                                                                                                                 |                                                                                                                                                                                                                                                                  |
| cursor `String`                                                                                                                                                                           | The cursor of a previous page of the section named by section. It is valid only together with section and with the same search, filters and sort as the request that issued it. Paging is offset-based, so results can shift if the incident is re-assessed between pages. A cursor at or past the end of its section is rejected with INVALID\_CURSOR.                                                                                        |                                                                                                                                                                                                                                                                  |
| search `String`                                                                                                                                                                           | Limits the response to rows matching this text, case-insensitively, in their title, identifier, resource, application, project, author, assignee, application tags or business unit names. Available fixes also match on their indicators. At most 200 characters.                                                                                                                                                                             |                                                                                                                                                                                                                                                                  |
| conditionalFilters [`[IncidentConditionalFilterInput!]`](https://docs.ox.security/api-documentation/api-reference/api--response-center/types/inputs/incident-conditional-filter-input.md) | Include and exclude filters, combined with AND across clauses. Supported field names are issue, application, appTag, businessUnit and fixType; other field names are ignored. The application filter matches the application name or the resource name. The fixType filter matches the upgrade type of pull requests and the fix type of available fixes; tickets have none, so an include clause hides them and an exclude clause keeps them. | <p>fieldName <code>String!</code><br>values <code>\[String!]!</code><br>condition <a href="https://docs.ox.security/api-documentation/api-reference/api--response-center/types/enums/incident-filter-condition.md"><code>IncidentFilterCondition!</code></a></p> |
| sortBy [`RemediationSortField`](https://docs.ox.security/api-documentation/api-reference/api--response-center/types/enums/remediation-sort-field.md)                                      | The column to sort by. A column that does not apply to a section leaves that section in its default order: newest activity first for pull requests and tickets, and worst severity first for available fixes.                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                  |
| sortOrder [`SortOrder`](https://docs.ox.security/api-documentation/api-reference/api--response-center/types/enums/sort-order.md)                                                          | The sort direction. It applies only together with sortBy. When absent, the direction is descending for Updated, Age and Severity and ascending for every other column.                                                                                                                                                                                                                                                                         |                                                                                                                                                                                                                                                                  |

### References

#### Queries using this object:

* [\<?> getIncidentRemediationPage.input](https://docs.ox.security/api-documentation/api-reference/api--response-center/queries/get-incident-remediation-page.md)
* [\<?> getIncidentRemediationFilters.input](https://docs.ox.security/api-documentation/api-reference/api--response-center/queries/get-incident-remediation-filters.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/api-documentation/api-reference/api--response-center/types/inputs/get-incident-remediation-page-input.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
