POST /api/samgov/entities/search
Price: 1 credit
Search SAM.gov registered entities (federal contractors) by name, NAICS, or state
Search active SAM.gov registered entities (U.S. federal contractors). Filter by legal business name, primary NAICS code, and physical-address state. Each result includes the entity UEI, legal business name, CAGE code, registration status and dates, addresses, incorporation and business structure, and business types.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results (min: 1)legal_business_name string nullable — Filter entities by legal business name (partial match)naics string nullable — Filter entities by primary NAICS codestate string nullable — Filter entities by physical-address US state or province code (e.g. CA)@type string (default: "SamgovEntity")uei_sam string requiredcage_code string nullabledodaac string nullablelegal_business_name string nullabledba_name string nullableentity_url string nullablesam_registered boolean nullableregistration_status string nullableuei_status string nullablepurpose_of_registration string nullableis_excluded boolean nullableregistered_at string nullableregistration_expires_at string nullableactivated_at string nullableupdated_at string nullableentity_start_date string nullablefiscal_year_end string nullablecongressional_district string nullableentity_structure string nullableorganization_structure string nullablebusiness_entity_type string nullableprofit_structure string nullablestate_of_incorporation string nullablecountry_of_incorporation string nullablebusiness_types array (default: [])primary_naics string nullablenaics array (default: [])@type string (default: "SamgovEntityNaics")code string nullabledescription string nullableis_primary boolean nullableis_small_business boolean nullablepsc array (default: [])@type string (default: "SamgovEntityPsc")code string nullabledescription string nullablephysical_address object nullable@type string (default: "SamgovEntityAddress")street_address string nullablestreet_address2 string nullablecity string nullablestate string nullablezip string nullablezip4 string nullablecountry string nullablemailing_address object nullable@type string (default: "SamgovEntityAddress")street_address string nullablestreet_address2 string nullablecity string nullablestate string nullablezip string nullablezip4 string nullablecountry string nullablepoints_of_contact array (default: [])@type string (default: "SamgovEntityPointOfContact")type string nullablefirst_name string nullablelast_name string nullableaddress object nullable@type string (default: "SamgovEntityAddress")street_address string nullablestreet_address2 string nullablecity string nullablestate string nullablezip string nullablezip4 string nullablecountry string nullable422 — The request body did not validate 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.