> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sanfoundation.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Responses and pagination

> Read SAN responses, follow result pages, and handle optional data.

Search, fetch, detail, status, and quote responses include `id` (request identifier), `took_ms` (processing time), and `request` (normalized parameters and defaults).

| Endpoint type | Data |
| - | - |
| Searches and reviews | `results`, `next_page` |
| Read a web page | `page` |
| Place details | `place` |
| Hotel details | `hotel` |
| Flight status | `status` |
| Flight booking options | `bookings` |
| Finance quote | `quote`, with additional blocks when available |
| Product details | `product` |

The [account endpoint](https://docs.sanfoundation.com/api-reference/account.md) returns fields directly. Errors use an [error object](https://docs.sanfoundation.com/guides/errors.md).

Start at `page=1`, preserve your parameters, and follow `next_page` until it is `null`. Each page costs one request. Page sizes are fixed; `limit`, `page_size`, and `offset` are unsupported. See each endpoint for page limits.

Flights, return options, and product search always have `next_page: null` and reject `page`. Other non-list endpoints are unpaginated. Positions start at 1 per page; deduplicate items when combining changing live results.

Only rely on required fields in the [API reference](https://docs.sanfoundation.com/api-reference/introduction.md). Optional data and result IDs can be absent. Empty `results` is successful and consumes quota.

Pass opaque result IDs unchanged to matching follow-up endpoints, only when present. Flight follow-ups also require the original route and dates.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.