/texas/companies/search

POST /api/texas/companies/search

Price: 1 credit

Search Texas business entities by name in the free Texas Comptroller Franchise Tax Account Status record. Matches from the start of the entity name and returns matching entities with name, taxpayer_id (Comptroller Taxpayer Number) and mailing-address ZIP. Use the taxpayer_id with texas/companies for the full entity record.

How to use it

Search Texas business entities by name (matched from the start of the name). Pass name and count. Returns a list of items, each with taxpayer_id (11-digit Comptroller Taxpayer Number), name and mailing_address_zip. Use the taxpayer_id with texas/companies for the full entity record (status, registered agent, officers).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Entity name to search by (matches from the start of the name) (examples: "WALMART", "WHATABURGER", "DELL COMPUTER"; minLength: 2; maxLength: 50)
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "TexasCompanySearchItem")
• taxpayer_id string required
• name string required
• mailing_address_zip string nullable

Errors

• 422 — The search name is too broad and matches too many entities — add more leading characters to narrow it 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 entities matched the search name 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.