# /fccid/authorizations/search

`POST /api/fccid/authorizations/search`

Price: 20 credits

Search FCC equipment authorizations by grantee code, product code, applicant, final action date, application purpose and status, equipment class, grant note codes, TCB and TCB scope, modular type, rule part, test firm, product description, frequency, emission designator, bandwidth, power output and tolerance. Each application carries the applicant, FCC ID, purpose, final action date, frequency ranges and links to its Form 731, exhibits, grant and correspondence.

## How to use it

Look up a device by its FCC ID with grantee_code plus product_code and is_product_code_exact; one FCC ID usually has several applications, the original grant and later permissive changes. `id` with `fcc_id` opens the full filing in fccid/authorizations and its documents in fccid/authorizations/exhibits.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `count` (integer, required) — Max number of applications to return (min: 1; max: 4000)
- `grantee_code` (string, nullable) — Grantee code, the leading part of an FCC ID (examples: "BCG")
- `product_code` (string, nullable) — Product code, the part of the FCC ID after the grantee code (examples: "A3427")
- `is_product_code_exact` (boolean) — Match product_code exactly instead of as a prefix (default: false)
- `applicant_name` (string, nullable) — Applicant name (examples: "Apple Inc.")
- `final_action_date_from` (string, nullable) — Earliest final action date (format: date; examples: "2026-01-01")
- `final_action_date_to` (string, nullable) — Latest final action date (format: date; examples: "2026-09-01")
- `application_purpose` (string, nullable) — Application purpose (one of: "original_grant", "class_ii_permissive_change", "class_iii_permissive_change", "change_in_fcc_id")
- `application_status` (string) — Application status; `granted` covers every granted status (default: "granted"; one of: "granted", "all", "grant_issued", "permissive_change_issued", "fcc_id_modification_issued", "dismissed", "denied")
- `tcb_scope` (string, nullable) — TCB scope the application was reviewed under (one of: "A1", "A2", "A3", "A4", "B1", "B2", "B3", "B4")
- `modular_type` (string, nullable) — Modular approval type (one of: "single", "limited_single", "split", "limited_split")
- `rule_part` (string, nullable) — FCC rule part (examples: "15C")
- `test_firm` (string, nullable) — Test firm name (examples: "TUV SUD")
- `product_description` (string, nullable) — Words from the product description as marketed (examples: "laptop")
- `lower_frequency_mhz` (number, nullable) — Lower frequency of an equipment line, MHz; requires upper_frequency_mhz (examples: 2402; min: 0)
- `upper_frequency_mhz` (number, nullable) — Upper frequency of an equipment line, MHz; requires lower_frequency_mhz (examples: 2480; min: 0)
- `equipment_class` (string, nullable) — Equipment class code as printed on the grant (one of: "5GB", "5GM", "5GT", "6CD", "6FC", "6FX", "6ID", "6PP", "6SD", "6VL", "6XD", "8CC", "8NC", "AIS", "AMP", "B2I", "B2P", "B2W", "B9A", "B9B", "BOS", "BPL", "CBD", "CBE", "CRD", "CRR", "CSR", "CVG", "CVO", "CVR", "CXX", "CYY", "DCD", "DSC", "DSR", "DSS", "DTS", "DWM", "DXX", "EAD", "EAV", "ETB", "ETR", "ETS", "FAP", "FDS", "FRB", "FRE", "FRF", "FRT", "GAT", "GEP", "GHF", "GHH", "GMF", "GVH", "HID", "JAB", "JAD", "JAV", "JBC", "JBP", "LMS", "LPR", "MRD", "MWR", "NII", "PCB", "PCE", "PCF", "PCT", "PLB", "PUB", "PUE", "PUF", "PUT", "RNV", "SRT", "SSA", "TBC", "TBF", "TBT", "TDC", "TLD", "TNB", "TNE", "TNF", "TNT", "UWB", "VRD", "WBT", "WG1", "WG2", "WGF", "WIT", "WMO", "WS1"; examples: "DTS")
- `grant_codes` (array, nullable) — Grant note codes of an equipment line, up to 3; an application must carry all of them (examples: ["CC","MO"]; maxItems: 3)
- `tcb_code` (string, nullable) — TCB code, the `id` of an fccid/tcbs/search row (examples: "US0101")
- `emission_designator` (string, nullable) — Emission class of an equipment line, without the bandwidth part (examples: "G1D")
- `bandwidth` (string, nullable) — Necessary bandwidth part of an emission designator (examples: "1M00")
- `power_output_w_from` (number, nullable) — Lowest power output of an equipment line, watts; requires power_output_w_to (min: 0)
- `power_output_w_to` (number, nullable) — Highest power output of an equipment line, watts; requires power_output_w_from (min: 0)
- `tolerance_from` (number, nullable) — Lowest frequency tolerance of an equipment line as filed; requires tolerance_to (min: 0)
- `tolerance_to` (number, nullable) — Highest frequency tolerance of an equipment line as filed; requires tolerance_from (min: 0)

## Response

### 200 — Successful Response

- `@type` (string) (default: "FccidAuthorization")
- `id` (string, required)
- `fcc_id` (string, required)
- `applicant_name` (string, nullable)
- `address` (string, nullable)
- `city` (string, nullable)
- `state` (string, nullable)
- `country` (string, nullable)
- `zip_code` (string, nullable)
- `application_purpose` (string, nullable)
- `final_action_date` (string, nullable)
- `is_tcb_approved` (boolean) (default: false)
- `frequency_ranges` (array) (default: [])
  - `@type` (string) (default: "FccidFrequencyRange")
  - `lower_mhz` (number, nullable)
  - `upper_mhz` (number, nullable)
- `form_url` (string, nullable)
- `exhibits_url` (string, nullable)
- `grant_url` (string, nullable)
- `correspondence_url` (string, nullable)

## Errors

### 422 — Validation Error

No search filter was given

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.