/missouri/companies/search

POST /api/missouri/companies/search

Price: 5 credits

Search Missouri business entities by name in the Missouri Secretary of State business registry. Returns matching entities with charter_number, name, legal_form, status, formed_date and registered_agent. Use the charter_number with missouri/companies for the full entity record.

How to use it

Search Missouri business entities by name. Pass keyword and count. match_mode controls name matching (starting_with, all_words, any_word, exact_match). Returns a list of items, each with charter_number (the public id with a type-letter prefix such as LC/FL/N/X, used as the lookup key for missouri/companies), name, legal_form (e.g. 'Limited Liability Company', 'Fictitious Name (Domestic)'), status (e.g. 'Active', 'Fictitious Expired'), formed_date and registered_agent. Use the charter_number with missouri/companies for the full entity record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Business name to search by (examples: "WALMART", "EDWARD JONES", "ANHEUSER-BUSCH"; minLength: 1; maxLength: 200)
• match_mode string — How the keyword is matched against business names (default: "0"; one of: "0", "1", "2", "3")
• count integer required — Max number of results to return (min: 1; max: 1000)

Response

• @type string (default: "MissouriCompanySearchItem")
• id string required
• charter_number string nullable
• name string nullable
• legal_form string nullable
• status string nullable
• formed_date string nullable
• registered_agent 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.