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

# Company Autocomplete reference

> Reference for Company Autocomplete: supported fields, filter operators, errors, and API summary.

Reference material for [Company Autocomplete](/company-docs/autocomplete/introduction):
common fields you can autocomplete, supported filter operators, errors, and
the API summary.

For walk-through examples, see [Company Autocomplete](/company-docs/autocomplete/introduction)
and [Examples](/company-docs/autocomplete/examples).

***

## Common fields to autocomplete

| Field                                        | Why you would use it                                                       |
| -------------------------------------------- | -------------------------------------------------------------------------- |
| `basic_info.industries`                      | Find exact industry labels before building industry filters.               |
| `basic_info.name`                            | Surface company names matching a partial string.                           |
| `basic_info.markets`                         | Discover indexed market labels (e.g. `NASDAQ`, `NYSE`).                    |
| `basic_info.employee_count_range`            | List the canonical employee-count bucket labels.                           |
| `taxonomy.professional_network_industry`     | Match primary industry values used in company search.                      |
| `taxonomy.professional_network_specialities` | Discover specialty tags used by the dataset.                               |
| `taxonomy.categories`                        | List the high-level category tags used by the dataset.                     |
| `locations.country`                          | Discover country values used by the indexed dataset.                       |
| `locations.headquarters`                     | Discover indexed HQ location strings.                                      |
| `basic_info.company_type`                    | Explore company type labels used in the dataset.                           |
| `funding.last_round_type`                    | Find valid funding stage labels before filtering by recent financing data. |
| `funding.investors`                          | Discover investor names indexed in the dataset.                            |
| `funding.tracxn_investors`                   | Discover the indexed investor-name vocabulary used by this filter alias.   |
| `revenue.acquisition_status`                 | List the indexed acquisition status labels.                                |
| `revenue.public_markets.stock_symbols`       | Discover indexed ticker symbols for public companies.                      |
| `revenue.public_markets.fiscal_year_end`     | Closed enum: returns the twelve calendar months in chronological order.    |

<Note>
  The `field` parameter accepts a broader set than this table — the table
  highlights the most useful fields for building filter dropdowns. For the
  full live allowlist, send a deliberately invalid `field` and read the
  `Valid fields` list returned in the `400` error. The shape of that error
  message is for debugging only and may change without notice.
</Note>

<Tip>
  `revenue.public_markets.fiscal_year_end` is a **closed-enum** static
  field — an empty `query` returns the twelve months
  (`January`...`December`) in chronological order without any backend
  lookup. Use it to populate a static fiscal-year-end dropdown without an
  extra round-trip.
</Tip>

***

## Supported filter operators

`=`, `!=`, `<`, `=<`, `>`, `=>`, `in`, `not_in`, `contains`.

<Warning>
  The operators `>=` and `<=` are **not supported**. Use `=>` and `=<`
  instead.
</Warning>

***

## Common errors and edge cases

If no values match your query, the API returns an empty array:

```json theme={"theme":"vitesse-black"}
{
    "suggestions": []
}
```

If you send an unsupported field name, the API returns a `400` with the list
of valid fields:

```json theme={"theme":"vitesse-black"}
{
    "error": {
        "type": "invalid_request",
        "message": "Field 'invalid_field' is not supported on scope 'company'. Valid fields: basic_info.company_type, basic_info.employee_count_range, basic_info.industries, basic_info.markets, basic_info.name, basic_info.primary_domain, ...",
        "metadata": []
    }
}
```

If that happens, double-check the field path against the supported list and
use a field that is available in the indexed Company Search schema.

***

## API reference summary

| Detail              | Value                                                             |
| ------------------- | ----------------------------------------------------------------- |
| **Endpoint**        | `POST /company/search/autocomplete`                               |
| **Auth**            | Bearer token + `x-api-version: 2025-11-01`                        |
| **Required params** | `field`, `query`                                                  |
| **Optional params** | `limit` (default: 20, max: 100), `filters`                        |
| **Response**        | `{ "suggestions": [{ "value": "..." }] }`                         |
| **Empty result**    | `200` with `"suggestions": []`                                    |
| **Errors**          | `400` (unsupported field), `401` (bad auth), `500` (server error) |

For pricing, see [Pricing](/general/pricing). For rate-limit guidance, see
[Rate limits](/general/rate-limits).

See the [full API reference](/openapi-specs/2025-11-01/introduction) for the
complete OpenAPI schema.