/missouri/companies/filings

POST /api/missouri/companies/filings

Price: 5 credits

List a Missouri business entity's filing history from the Missouri Secretary of State business registry by charter number: each filing's type, name, filing and effective dates, and the document reference for the scanned filing image.

How to use it

List the filing history of one Missouri business entity by its charter number (e.g. 'X00536736'). Returns one item per filing with type (e.g. Creation, Renewals, Administrative - Judicial Actions), name (the specific filing, e.g. 'Application for Fictitious Name Registration'), filed_at, effective_date, and document_id/document_version that identify the scanned filing image.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• charter_number string required — Missouri business charter number (the public id, e.g. LC0014881, FL0019537, N000706187, X00536736) (examples: "LC0014881", "FL0019537", "N000706187", "X00536736"; minLength: 1; maxLength: 30)

Response

• @type string (default: "MissouriFiling")
• type string nullable
• name string nullable
• filed_at string nullable
• effective_date string nullable
• document_id string nullable
• document_version 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 (no entity exists for this charter 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.