---
title: "Get custom data for a carrier"
method: GET
path: "/v1/carriers/{dot_number}/custom-data"
---

# Get custom data for a carrier

`GET /v1/carriers/{dot_number}/custom-data`

The account’s custom-data record for one carrier. A miss returns 200 with found: false, never 404. Leading-zero requests are retried with zeros stripped (one direction only); the response echoes the requested dot_number.

## Path parameters

- `dot_number` string, required

## Response `200`

Record, or a found: false sentinel

- CustomDataCarrierResponse
  - `dot_number` string, required — Echoes the requested value
  - `found` boolean, required
  - `custom_data` object, nullable — null when found is false
  - `updated_at` string, date-time, nullable
  - `fields` CustomDataField[], required
    - `field_key` string — Key used inside custom_data objects and in POST /v1/custom-data/lookup field projections
    - `display_name` string, nullable
    - `data_type` string, nullable — e.g. number, boolean, text — from the account’s CRM configuration

## Other responses

- `400` — Invalid parameters
- `401` — Invalid or missing API key
- `403` — Custom data is not enabled for this account. Not an auth failure and not transient — do not retry with backoff; probe GET /v1/custom-data/fields instead.
- `429` — Too many requests. Check X-RateLimit-Remaining and Retry-After headers.
- `503` — The account’s custom data configuration is invalid. Contact support; retrying will not help.

---

[API](https://skmtc.net/runalphaloops/apis/alphaloops-fmcsa-carrier-data-api.md) · [All operations](https://skmtc.net/runalphaloops/apis/alphaloops-fmcsa-carrier-data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/runalphaloops/alphaloops-fmcsa-carrier-data-api/revisions/ae58c064a7af/schema)