# Page Not Found

The URL `2025-release-notes/july-10-2025-orchestration-api-get-list-and-get-stats-routes` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [July 10, 2025 - Orchestration API - GET List and GET Stats routes](https://doc.batch.com/release-notes/release-notes/july-10-2025-orchestration-api-get-list-and-get-stats-routes.md)
- [April 13, 2026 - Orchestrations API Updates](https://doc.batch.com/release-notes/release-notes/april-13-2026-orchestrations-api-updates.md)
- [June 30, 2025 - Targeting on Installation and App version native attributes](https://doc.batch.com/release-notes/release-notes/june-30-2025-targeting-on-installation-and-app-version-native-attributes.md)
- [July 21, 2025 - Display all devices in the Profile view](https://doc.batch.com/release-notes/release-notes/july-21-2025-display-all-devices-in-the-profile-view.md)
- [July 24, 2025 -Extended event display in Profile View](https://doc.batch.com/release-notes/release-notes/july-24-2025-extended-event-display-in-profile-view.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://doc.batch.com/release-notes/release-notes/july-10-2025-orchestration-api-get-list-and-get-stats-routes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://doc.batch.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://doc.batch.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/release-notes/release-notes/july-10-2025-orchestration-api-get-list-and-get-stats-routes.md`).

You may also use `Accept: text/markdown` header for content negotiation.