/fccid/grantees/search

POST /api/fccid/grantees/search

Price: 10 credits

Search FCC grantees, the companies registered to hold FCC IDs, by grantee code, name, city, state, country and zip code. Each grantee carries its code, name, mailing address, contact name and the date the code was received.

How to use it

A grantee `id` is the grantee code that starts every FCC ID it holds; pass it as grantee_code to fccid/authorizations/search to list the company's devices.

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 grantees to return (min: 1; max: 3000)
• grantee_code string nullable — Grantee code (examples: "BCG")
• name string nullable — Grantee name (examples: "Apple")
• city string nullable — City (examples: "Cupertino")
• state string nullable — US state or territory, two-letter postal code (examples: "CA"; pattern: ^[A-Za-z]{2}$)
• country string nullable — Country, two-letter code (examples: "US"; pattern: ^[A-Za-z]{2}$)
• zip_code string nullable — Zip or postal code (examples: "95014")

Response

• @type string (default: "FccidGrantee")
• id string required
• name string nullable
• address string nullable
• po_box string nullable
• city string nullable
• state string nullable
• country string nullable
• zip_code string nullable
• contact_name string nullable
• received_date string nullable
• applicant_id string nullable
• exhibits_url string nullable

Errors

• 422 — No search filter was given Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.