> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/order-search-options.md).

# Order search options

Use the **OrderSearchOptions** object to configure your search order options via JSON-RPC API 6.0.

## Request parameters <a href="#object-parameters" id="object-parameters"></a>

<table><thead><tr><th width="180.933349609375">Parameter</th><th>Type / Description</th></tr></thead><tbody><tr><td><code>ApproveStatus</code></td><td><p><strong>Optional (string)</strong></p><p>The desired approved status. Available values: WAITING, OK, FRAUD, INVALIDDATA.</p></td></tr><tr><td><code>Newer</code></td><td><strong>Optional (string)</strong><br>Needed timestamp. If not provided, will return by default the data for the last 7 days.</td></tr><tr><td><code>Status</code></td><td><strong>Optional (string)</strong><br>Order status. Some of the available options are COMPLETE, PENDING, CANCELED, REFUND.</td></tr><tr><td><code>StartDate</code></td><td><strong>Optional (string)</strong><br>Start date in format Y-m-d. Will overwrite Newer if provided.</td></tr><tr><td><code>EndDate</code></td><td><strong>Optional (string)</strong><br>End date in format Y-m-d.</td></tr><tr><td><code>PartnerOrders</code></td><td><strong>Optional (boolean)</strong><br>Decide if it will also include partner orders.</td></tr><tr><td><code>ExternalRefNo</code></td><td><strong>Optional (string)</strong><br>The external reference number of the order.</td></tr><tr><td><code>IncludeTestOrders</code></td><td><p><strong>Optional (string)</strong></p><p>Should test orders be included in the result:</p><p>Values:</p><ul><li>YES -  test orders are included</li><li>NO - test orders are not included</li><li>ONLY - only the test orders are included</li></ul></td></tr><tr><td><code>CcLastDigits</code></td><td><p><strong>Optional (string)</strong></p><p>The last 4 digits of the credit card used for payment.</p></td></tr><tr><td><code>Pagination</code></td><td><p><strong>Optional (object)</strong></p><p>Existing shipping class object with the structure detailed below.</p></td></tr><tr><td><code>Pagination.Limit</code></td><td><p><strong>Optional (int)</strong></p><p>The number of results to be returned</p></td></tr><tr><td><code>Pagination.Page</code></td><td><p><strong>Optional (int)</strong></p><p>The page number</p></td></tr></tbody></table>


---

# 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.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/order-search-options.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.
