/arizona/filings/search

POST /api/arizona/filings/search

Price: 5 credits

Search filings submitted to the Arizona Corporation Commission by business name or entity number: work order number, filing type, business name, processing status, submitting party (filing agent) and the date the filing was received. Covers pending and processed submissions such as annual reports, foreign registration statements and certificate requests.

How to use it

Look up filings submitted to the Arizona Corporation Commission for a business. Pass count plus either name (with optional search_method starts_with/contains/exact) or entity_number. Returns a list of items, each with work_order_number, name, filing_type (for example Annual Report, Certificate of Good Standing), status (Approved/Pending/...), submitter_name (the filing agent, e.g. C T CORPORATION SYSTEM), received_at (ISO datetime), work_order_id, transaction_id and guid. Returns an empty list when nothing matches.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "ArizonaFiling")
• work_order_number string required
• name string nullable
• filing_type string nullable
• status string nullable
• submitter_name string nullable
• received_at string nullable
• work_order_id integer nullable
• transaction_id integer nullable
• guid 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.