/utah/companies

POST /api/utah/companies

Price: 5 credits

Get a Utah business's registry record from the Division of Corporations and Commercial Code by its Entity Number: name, entity type, subtype, profession, status, status details, formation and renewal dates, domicile and jurisdiction (for foreign entities), registered agent (name, status, address), principals/officers (title, name, address) and physical/mailing addresses.

How to use it

Look up one Utah business by its Entity Number (e.g. '14058748-0151', or the bare '14058748'). Returns one item with entity_number, name, legal_form (entity type), subtype, status, formation_date, jurisdiction, registered_agent, principals (officers) and physical/mailing addresses. To find an Entity Number by company name, use utah/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• entity_number string required — Utah business Entity Number (examples: "14058748-0151", "6085119-0143", "12400197"; minLength: 1)

Response

• @type string (default: "UtahCompany")
• entity_number string required
• business_id string required
• name string nullable
• legal_form string nullable
• subtype string nullable
• status string nullable
• status_details string nullable
• status_updated_at string nullable
• jurisdiction string nullable
• formation_date string nullable
• formation_effective_date string nullable
• renew_by_date string nullable
• last_renewed_date string nullable
• registered_agent object nullable
  • @type string (default: "UtahRegisteredAgent")
  • name string nullable
  • entity_number string nullable
  • status string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • updated_at string nullable
• principals array (default: [])
  • @type string (default: "UtahPrincipal")
  • name string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • updated_at string nullable
• physical_address object nullable
  • @type string (default: "UtahAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • updated_at string nullable
• mailing_address object nullable
  • @type string (default: "UtahAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • updated_at 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 — No business found for the given Entity 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.