/texas/companies

POST /api/texas/companies

Price: 1 credit

Get a Texas business entity by its Comptroller Taxpayer Number (11 digits) from the free Texas Comptroller Franchise Tax Account Status record: legal name, Federal EIN, DBA name, franchise-tax right-to-transact status, state of formation, Secretary-of-State registration status and effective date, SoS file number, registered agent name, mailing and registered-office addresses, report year and officer/director records (name, title, address).

How to use it

Get one Texas business entity by its Comptroller Taxpayer Number (11 digits). Returns one item with taxpayer_id, name, fei_number (Federal EIN), dba_name, right_to_transact (franchise-tax status, e.g. ACTIVE / FRANCHISE TAX ENDED), state_of_formation, sos_registration_status (ACTIVE/INACTIVE), effective_sos_registration_date (MM/DD/YYYY), sos_file_number, registered_agent_name, mailing_address and registered_office_address (street, city, state, postal_code, postal_code_ext), report_year and officers (name, title, active_year, street, city, state, postal_code, source). Use texas/companies/search to find the taxpayer number by name.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• taxpayer_id string required — Texas Comptroller Taxpayer Number (11 digits) (examples: "32029266908", "17423222086"; minLength: 1)

Response

• @type string (default: "TexasCompany")
• taxpayer_id string required
• name string required
• fei_number string nullable
• dba_name string nullable
• right_to_transact string nullable
• state_of_formation string nullable
• sos_registration_status string nullable
• effective_sos_registration_date string nullable
• sos_file_number string nullable
• registered_agent_name string nullable
• mailing_address object nullable
  • @type string (default: "TexasAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • postal_code string nullable
  • postal_code_ext string nullable
• registered_office_address object nullable
  • @type string (default: "TexasAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • postal_code string nullable
  • postal_code_ext string nullable
• report_year string nullable
• officers array
  • @type string (default: "TexasOfficer")
  • name string nullable
  • active_year string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • postal_code string nullable
  • source 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 (well-formed but nonexistent Taxpayer 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.