/arkansas/companies

POST /api/arkansas/companies

Price: 1 credit

Get an Arkansas business's registry record from the Secretary of State by its filing number: exact name, entity type, status, statute filed under, filing date, principal address, registered agent (name and address), fictitious/DBA names, officers (name and role), and for foreign entities the foreign name, foreign address and state of origin.

How to use it

Look up one Arkansas business by its filing number (e.g. '100067582'). Returns one item with filing_number, name, legal_form, status, filed_under_act, filed_at, principal_address, registered_agent, registered_agent_address, aliases (fictitious/DBA names), officers (name and role), and foreign_name, foreign_address, state_origin for foreign entities. To find a filing number by company name, use arkansas/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• filing_number string required — Arkansas business filing number (examples: "100067582", "811168172")

Response

• @type string (default: "ArkansasCompany")
• filing_number string required
• name string nullable
• legal_form string nullable
• status string nullable
• filed_under_act string nullable
• filed_at string nullable
• principal_address string nullable
• registered_agent string nullable
• registered_agent_address string nullable
• aliases array (default: [])
• officers array (default: [])
  • @type string (default: "ArkansasOfficer")
  • name string required
  • role string nullable
• foreign_name string nullable
• foreign_address string nullable
• state_origin string 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 filing 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.