---
cuppy_hub: salesforce
cuppy_path: reference/official/data360/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-rows.md
cuppy_section: docs
cuppy_doc: GZFE-RD95
cuppy_doc_uuid: 4b5a132c-5e9e-4b0b-a53e-a812af3061fe
cuppy_permalink: https://cuppy.io/salesforce/d/GZFE-RD95
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-rows
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: b5c1b0cdfb2c1adbb5c87dfb8645cc350cf9633d70e4196211a21332242f6f9b
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---

> Mirror of <https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-rows.html> (Salesforce, Data 360 Query Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers.

## Get SQL Query Rows

Use the `GET /api/v3/query/{queryId}/rows` endpoint of the Data 360 Query API to retrieve results from a completed query using offset-based pagination. Use this endpoint to page through large result sets by specifying an `offset` and optional `limit` or `byteLimit`. Responses are available in JSON or Apache Arrow format.

*   **HTTP Method**: GET
*   **Format**: REST
*   **URI**: `/api/v3/query/{queryId}/rows`

| Parameter | Type | Description |
| --- | --- | --- |
| `queryId` | string | Required. The unique identifier of the query returned from `POST /api/v3/query`. Example: `MTAuMjcuMTgxLjE0OTo3NDg0_1cfc8d35`. |

| Parameter | Required | Type | Description |
| --- | --- | --- | --- |
| `offset` | Yes | integer | Row offset to start from. |
| `limit` | No | integer | Maximum number of rows to return. |
| `byteLimit` | No | integer | Maximum bytes to return. Default and maximum is 20 MB (`20000000`). |
| `omitSchema` | No | boolean | `true` to omit schema metadata from the response. Default `false`. |

| Header | Value |
| --- | --- |
| `Authorization` | `Bearer {accessToken}` |
| `Accept` | `application/json` or `application/vnd.apache.arrow.stream` |

| Field | Description |
| --- | --- |
| `metadata` | Object containing column schema. Not included when `omitSchema=true`. |
| `data` | Array of result rows, where each row is an array of values ordered by the `metadata.columns` schema. |
| `returnedRows` | Number of rows returned in this response. Arrow responses omit this field. |

This example shows a row retrieval request and response.

Set `Accept: application/vnd.apache.arrow.stream` to receive results as a binary Arrow IPC stream instead of JSON. Arrow is recommended for large result sets — it reduces payload size and deserialization overhead compared to JSON. The `omitSchema` query parameter has no effect on Arrow responses; the schema is always embedded in the Arrow stream.

For large result sets, [Get SQL Query Chunks](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-chunk.html) is the preferred retrieval method.

*   [Submit SQL Query](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-post.html)
*   [Get SQL Query Status](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-query.html)
*   [Get SQL Query Chunks](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/query-api-v3-get-chunk.html)
*   [Query Services Status Codes](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/c360a-api-queryservices-statuscodes.html)


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->