/arizona/companies/search

POST /api/arizona/companies/search

Price: 10 credits

Search Arizona business entities by name in the Arizona Corporation Commission registry. Returns matching entities with entity number, registered name, business status, legal form, domestic/foreign region type, the known place of business address and, for name reservation/registration records, the applicant name and contact e-mail.

How to use it

Search Arizona business entities by name. Pass name and count; optionally search_method (starts_with/contains/exact). Returns a list of items, each with entity_number, name, status, legal_form, region_type, address (full, street, street2, city, state, zip, country) and applicant_name / applicant_email (filled on Name Reservation and Name Registration records). Returns an empty list when nothing matches. Use entity_number with arizona/companies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Business name to search for (examples: "WALMART", "DESERT JUICE"; minLength: 2)
• count integer required — Max number of results to return (min: 1)
• search_method string — Name matching mode (default: "starts_with"; one of: "starts_with", "contains", "exact")

Response

• @type string (default: "ArizonaCompany")
• entity_number string required
• name string required
• status string nullable
• legal_form string nullable
• region_type string nullable
• applicant_name string nullable
• applicant_email string nullable
• address object nullable
  • @type string (default: "ArizonaAddress")
  • full string nullable
  • street string nullable
  • street2 string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country 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 — 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.

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.