/georgia/companies

POST /api/georgia/companies

Price: 1 credit

Get a Georgia business entity by its control number from the Secretary of State Corporations Division registry: legal name, control number, entity type, status, NAICS industry classification, principal office address, formation/registration date, dissolved date, jurisdiction, last annual registration year, registered agent (name, physical address, county) and officer records (name, title, business address).

How to use it

Get one Georgia business entity by its control number (the public registration number; find it with georgia/companies/search). Returns one item with name, control_number, legal_form (e.g. Domestic Limited Liability Company, Foreign Profit Corporation), status (e.g. Active/Compliance, Withdrawn, Admin. Dissolved), naics_code and naics_sub_code (industry classification, present mainly on partnerships and some LLCs), principal_office_address, formation_date (M/D/YYYY), dissolved_date (M/D/YYYY, set when the entity is dissolved/terminated), jurisdiction (state or country of formation), last_annual_registration_year, registered_agent (name, address, county) and officers (name, title, address). Use georgia/companies/filings for the entity's filing history.

Parameters

• access-token string required

Request body

• timeout 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)

Response

• @type string (default: "GeorgiaCompany")
• business_id string required
• name string required
• control_number string nullable
• legal_form string nullable
• status string nullable
• naics_code string nullable
• naics_sub_code string nullable
• principal_office_address string nullable
• formation_date string nullable
• dissolved_date string nullable
• jurisdiction string nullable
• last_annual_registration_year string nullable
• registered_agent object nullable
  • @type string (default: "GeorgiaRegisteredAgent")
  • name string nullable
  • address string nullable
  • county string nullable
• officers array
  • @type string (default: "GeorgiaOfficer")
  • name string nullable
  • address string nullable

Errors

• 422 — 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.

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.