---
title: "Batch custom-data lookup"
method: POST
path: "/v1/custom-data/lookup"
---

# Batch custom-data lookup

`POST /v1/custom-data/lookup`

Custom-data records for up to 500 DOT numbers in one call. Records come back under the requested DOT number; misses are listed in missing_dot_numbers. Optional fields projection narrows the returned custom_data keys.

## Request body

- CustomDataLookupRequest
  - `dot_numbers` string[], required — 1-500 DOT numbers; numbers are coerced to strings
  - `fields` string[] — Optional projection: subset of the account’s field keys. Unknown keys return 400.

## Response `200`

Batch results with found/missing partition

- CustomDataLookupResponse
  - `requested_count` integer — After deduplication
  - `found_count` integer
  - `records` CustomDataRecord[]
    - `dot_number` string — Echoes the requested DOT number
    - `custom_data` object — Only the account’s enabled fields, keyed by field_key. Missing values are null.
    - `updated_at` string, date-time, nullable — When the record was last loaded into AlphaLoops (not real-time CRM state)
  - `missing_dot_numbers` string[] — Requested DOTs with no record, echoed as requested

## 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)