---
title: "Business special requests"
description: "Business list and detail operations use params both for sparse fields and for operation-specific relation or computed-field expansions."
canonical: https://docs.ordering.co/api-reference/guides/business-special-requests/
---

# Business special requests

Business list and detail operations use `params` both for sparse fields and for operation-specific relation or computed-field expansions. These expansions are not a universal Business schema: use only the values supported by the exact operation and operation version.

## Common expansions

Available expansions include:

| `params` value                                | Context returned when supported                                                             |
| --------------------------------------------- | ------------------------------------------------------------------------------------------- |
| `menus`                                       | Menus and, depending on the operation and mode, their category/product tree.                |
| `city`                                        | The related city; the response also includes `city_id`.                                     |
| `reviews`                                     | Review aggregates and related review data.                                                  |
| `gallery`                                     | Business gallery items.                                                                     |
| `offers`                                      | Offers visible under the current mode, project features, and caller.                        |
| `categories`, `products`, `products_featured` | Catalog relations. Use the `products_featured` token; `featured_products` is not supported. |
| `zones`                                       | Delivery-zone and delivery calculation context.                                             |
| `webhooks`                                    | Business webhooks on operations that permit this relation. The current token is plural.     |
| `paymethods`                                  | Business payment methods. Sensitive credential fields may be omitted from the response.     |
| `available_drivers_count`                     | Availability counts calculated for the selected business/search context.                    |

Additional expansions may include `owners`, `agents`, `types`, `configs`, `taxes`, and `third_party_integrations`. Their availability and visibility depend on list or detail version, mode, caller, and project features; do not assume they are available on every response.

## Search context

Public business discovery can combine an order `type`, a `location` or dropdown selection, and `params=zones`. For example:

```text
GET https://api.ordering.co/v400/en/YOUR_PROJECT/business?type=1&location=40.7539143,-73.9810162&params=zones,name,slug
```

```json
{
  "error": false,
  "result": [
    {
      "id": 22,
      "name": "Example business",
      "timezone": "America/New_York",
      "open": false,
      "distance": 0,
      "delivery_zone": 15,
      "minimum": 1,
      "delivery_price": 2
    }
  ]
}
```

This is an illustrative shape, not a complete response schema. Location, order type, dropdown, schedule, site, and project settings can affect eligibility and calculated fields.

## Dashboard mode

`mode=dashboard` exposes administrative shapes and is access-controlled. List and detail paths may use different role checks: do not infer access to one from access to the other. The published API reference contract remains authoritative.

For the base resource fields, see [Business model](https://docs.ordering.co/api-reference/guides/business-model/). The related endpoint guides are [Find a business](https://docs.ordering.co/api-reference/guides/get-business/) and [List businesses](https://docs.ordering.co/api-reference/guides/get-businesses/).