POST /api/georgia/companies/search
Price: 1 credit
Search Georgia business entities in the Secretary of State Corporations Division registry by business name or control number. Returns matching entities with name, control number, entity type, status, principal office address and registered agent name. Use the control_number with georgia/companies for the full entity record.
Search Georgia business entities by business name or control number. Pass query, count, and optionally search_type (business_name, control_number) and search_criteria (starts_with, contains, exact_match). Returns a list of items, each with name, control_number (the public registration number — the lookup key for georgia/companies), legal_form (e.g. Domestic Limited Liability Company, Foreign Profit Corporation, Name Reservation), status (e.g. Active/Compliance, Withdrawn, Admin. Dissolved, Terminated, Expired), principal_office_address and registered_agent_name. Returns an empty list when nothing matches. Use the control_number with georgia/companies for officers, registered agent and addresses.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)query string required — Business name or control number to search by (examples: "WALMART", "Coca-Cola", "K630997"; minLength: 1; maxLength: 200)search_type string — Which field to match the query against (default: "business_name"; one of: "business_name", "control_number")search_criteria string — How to match the query against the field (default: "contains"; one of: "starts_with", "contains", "exact_match")count integer required — Max number of results to return (min: 1)@type string (default: "GeorgiaCompanySearchItem")business_id string requiredname string requiredcontrol_number string nullablelegal_form string nullablestatus string nullableprincipal_office_address string nullableregistered_agent_name 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.