/alabama/companies

POST /api/alabama/companies

Price: 1 credit

Get an Alabama business's registry record from the Secretary of State by its entity ID number: exact name, entity type, status (with the date it took effect and any successor it merged or consolidated into), place and date of formation, principal and mailing addresses, registered agent (name and addresses), nature of business, authorized and paid-in capital, incorporators or members (name and addresses), the years annual reports were filed, the transaction history (dated changes to agent, name, address, etc.), and recorded documents (date, type and page count). For foreign entities also the home-state legal name and service-of-process address.

How to use it

Look up one Alabama business by its entity ID number (e.g. '000900608', accepts dashed '000-900-608'). Returns one item with entity_id, name, legal_form, status, status_date, successor, foreign_legal_name, place_of_formation, formation_date, qualify_date, principal_address, principal_mailing_address, registered_agent, registered_office_address, registered_office_mailing_address, service_of_process, nature_of_business, capital_authorized, capital_paid_in, officers (name, role, address, mailing_address), annual_report_years, transactions (date, description, detail) and recorded_documents (date, type, page_count). To find an entity ID by company name, use alabama/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• entity_id string required — Alabama Secretary of State entity ID number (examples: "000900608", "000-900-608")

Response

• @type string (default: "AlabamaCompany")
• entity_id string required
• name string nullable
• legal_form string nullable
• status string nullable
• status_date string nullable
• successor string nullable
• foreign_legal_name string nullable
• place_of_formation string nullable
• formation_date string nullable
• qualify_date string nullable
• principal_address string nullable
• principal_mailing_address string nullable
• registered_agent string nullable
• registered_office_address string nullable
• registered_office_mailing_address string nullable
• service_of_process string nullable
• nature_of_business string nullable
• capital_authorized string nullable
• capital_paid_in string nullable
• officers array (default: [])
  • @type string (default: "AlabamaOfficer")
  • name string required
  • role string nullable
  • address string nullable
  • mailing_address string nullable
• annual_report_years array (default: [])
• transactions array (default: [])
  • @type string (default: "AlabamaTransaction")
  • date string nullable
  • description string nullable
  • detail string nullable
• recorded_documents array (default: [])
  • @type string (default: "AlabamaDocument")
  • date string nullable
  • type string nullable
  • page_count integer nullable
• url string required

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 — No business found for the given entity ID 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.