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

# Make your first TruckerFetch API call

> Create a scoped Pro API key, verify your account access and search a small carrier page while preserving source dates and pagination metadata.

TruckerFetch REST requests use your Pro account and a scoped API key. This quickstart reads account access, then searches a small catalog page without creating an export or opening historical dates.

**1. Create a scoped key**

Sign in to [API keys](https://truckerfetch.com/dashboard/api/keys). Create a purpose-specific key with `data:read`. Add `contacts:read` only if your integration needs permitted contact fields. Copy the secret when it is shown and store it in your application's secret manager.

**2. Set your local environment**

Provide the key outside source control. Do not paste a real key into shared prompts, issues, example files or URLs.

```bash theme={null}
export TRUCKERFETCH_API_KEY='your-api-key'
```

**3. Check account access**

```bash theme={null}
curl --fail-with-body --silent --show-error \
  'https://truckerfetch.com/api/v1/account' \
  -H "Authorization: Bearer $TRUCKERFETCH_API_KEY"
```

A successful JSON response has `data` and `meta.request_id`. Save the request ID when troubleshooting.

**4. Search carriers**

```bash theme={null}
curl --fail-with-body --silent --show-error \
  'https://truckerfetch.com/api/v1/carriers/search' \
  -H "Authorization: Bearer $TRUCKERFETCH_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"filters":{"states":["TX"]},"limit":10}'
```

Read the rows in `data` and the source metadata in `meta`. If the response includes `next_cursor`, send it with the same filters to request the next page. An empty page is a valid result.

## Continue your integration

Use [carrier search](/docs/guides/carrier-search.md) for filters and cursor recovery. Use [exports](/docs/guides/exports.md) when you need a pinned CSV rather than many interactive pages. See [errors](/docs/errors.md) for `401`, `402`, `403` and retry behavior.


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