---
title: "Read query results by offset"
method: GET
path: "/v1/query/results"
tags: ["Queries"]
---

# Read query results by offset

`GET /v1/query/results`

## Request

- Base URL: `https://blobsrus.omniapp.co/api`
- URL: `https://blobsrus.omniapp.co/api/v1/query/results`
- Auth: HTTP bearer

Read a completed job's stored result by raw byte offset. See [Reading large results](/api/queries/run-query#reading-large-results) for the full flow with `completionOnly`.

Results stay readable for about an hour after the job completes. Reading a job that hasn't completed yet, or whose result has expired, returns an error status on the job line.

## Query parameters

- `jobId` string, uuid, required
- `offset` integer
- `maxBytes` integer
- `timeoutMs` integer

## Response `200`

The requested byte window of the job's result, streamed as newline-delimited JSON (`text/ndjson`): one job line, then a footer line. The response as a whole cannot be parsed as a single JSON document — parse it line by line.

## Other responses

- `400`: Bad Request. Possible causes: - `jobId` is missing or not a valid UUID - `offset` is negative or not an integer - `maxBytes` or `timeoutMs` is zero, negative, or not an integer
- `401`: Missing or invalid authentication
- `429`: Too Many Requests - Rate limit exceeded (60 requests/minute)
- `500`: Error reading query results

## Changes

- **2026-11-03** `43290040f88f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/omni/apis/omni-api/changes/v1/query/results/get.md)

---

[API](https://skmtc.dev/omni/apis/omni-api.md) - [All operations](https://skmtc.dev/omni/apis/omni-api/llms.txt) - [OpenAPI document](https://skmtc.dev/omni/apis/omni-api/revisions/43290040f88f?raw)