POST /api/georgia/companies/filings
Price: 1 credit
Get the filing history of a Georgia business entity by its control number from the Secretary of State Corporations Division registry. Returns filings with filing number, filing type (e.g. Business Formation, Annual Registration, Business Amendment, Business Withdrawal), filing date and effective date.
Get the filing history of a Georgia business entity by its control number (find it with georgia/companies/search). Pass control_number and count. Returns a list of filings, each with filing_number, filing_type (e.g. Business Formation, Annual Registration (YYYY), Business Amendment, Business Withdrawal), filed_at (M/D/YYYY) and effective_date (M/D/YYYY).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)control_number string required — Georgia control number (the public registration number shown on the entity record) (examples: "K630997", "14111592", "0056814"; minLength: 1; maxLength: 30)count integer required — Max number of filings to return (min: 1)@type string (default: "GeorgiaFiling")filing_number string requiredfiling_type string nullablefiled_at string nullableeffective_date 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 — Entity not found (well-formed but nonexistent control number) 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.