---
title: "List records missing a field"
method: GET
path: "/v1/data/gaps/records"
tags: ["Data Quality"]
---

# List records missing a field

`GET /v1/data/gaps/records`

## Request

- Base URL: `https://api.gunspec.io`
- URL: `https://api.gunspec.io/v1/data/gaps/records`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

The ids lacking a given field, paginated. This is the half a machine consumes: ask which manufacturers have no website, get the ids back, hand them to whatever fills them in.

A field the entity does not track is a 400 naming the ones it does. It is deliberately not an empty page: nothing missing reads as a clean bill of health, and a caller who mistyped a column name would believe it.

**Requires Enterprise tier or higher.**

## Query parameters

- `entity` 'manufacturers' | 'firearms' | 'calibers' | 'attachments' | 'ammunition', required
- `field` string, required
- `page` integer
- `per_page` integer

## Response `200`

List records missing a field

- object
  - `success` boolean, required: Always true on a successful response. Every error carries `false` and an `error` object instead.
  - `data` object[], required: One page of results. Use `pagination` to walk the rest.
    - `id` string: Slug of the record.
    - `name` string: Its name, so a worklist is readable without a second lookup.
    - `field` string: The field this row is missing. Echoed so a stored batch still says what it was collected for.
    - `value` string, nullable: What the record holds in that field. Always null here: the query selects records missing it, so this says "no value" rather than "not looked at".
    - `sources` string[]: The pages the record already cites. Carried so a consumer can judge whether the missing value is findable without fetching the record first.
  - `pagination` Pagination: Page-size is reported under both `per_page` (matching the request parameter) and `limit` (retained for existing integrations). They always carry the same value. `total` and `totalPages` are omitted for Explorer and anonymous callers.
    - `page` integer, required: The page this response is, 1-based.
    - `per_page` integer, required: Page size. Same value as `limit`.
    - `limit` integer, required: Page size. Alias of `per_page`.
    - `total` integer: Total records matching the query across every page.
    - `totalPages` integer: How many pages the result set spans at the current `per_page`.

## Other responses

- `400`: Validation error
- `401`: Missing or invalid API key
- `403`: The credential is valid and the caller is not permitted. Three causes, none of which reissuing a key changes: the plan is below the endpoint's tier, the account is suspended, or the key is not attached to the thing being acted on, meaning a user account for `/v1/me` or a shop for `/v1/vendor`. Distinct from 401, which means the credential is missing, malformed or expired and a new one can work.
- `429`: A limit was reached. `RATE_LIMITED` is the per-minute limit: wait `Retry-After` seconds (a minute) and retry. `DAILY_CAP_EXCEEDED` is the plan's daily limit, per key: nothing will be served until the counters return to zero at midnight UTC. `MONTHLY_CAP_EXCEEDED` is the plan's monthly allowance, for the whole account: nothing will be served until midnight UTC on the first of next month, or until the plan changes. For both, `Retry-After` is the seconds until then and `error.resetsAt` says when as an instant. Calls made after a refusal are refused too and do not spend the month, and a free key that keeps calling is paused, so stop at the first one and resume at the reset.
- `500`: Internal server error

---

[API](https://skmtc.dev/gunspec/apis/gunspec-io-api.md) · [All operations](https://skmtc.dev/gunspec/apis/gunspec-io-api/llms.txt) · [OpenAPI document](https://skmtc.dev/gunspec/apis/gunspec-io-api/revisions/f2e974d8b05c?raw)