/colorado/companies

POST /api/colorado/companies

Price: 1 credit

Get a Colorado business's registry record from the Secretary of State business database by its ID number: name, status, entity type, formation date, jurisdiction, periodic report month, principal office and mailing addresses, and the registered agent (name, street and mailing address).

How to use it

Look up one Colorado business by its ID number (e.g. '20061264050'). Returns one item with id, name, status (e.g. 'Good Standing', 'Voluntarily Dissolved', 'Delinquent'), legal_form (entity type such as 'Limited Liability Company', 'Nonprofit Corporation', 'Foreign Corporation'), formation_date, jurisdiction, periodic_report_month, principal_address, mailing_address and registered_agent. To find an ID number by company name, use colorado/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Colorado business ID number (examples: "20061264050", "20258295695", "20021320545"; minLength: 1)

Response

• @type string (default: "ColoradoCompany")
• id string required
• name string nullable
• status string nullable
• legal_form string nullable
• formation_date string nullable
• jurisdiction string nullable
• periodic_report_month string nullable
• principal_address object nullable
  • @type string (default: "ColoradoAddress")
  • full string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
• mailing_address object nullable
  • @type string (default: "ColoradoAddress")
  • full string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
• registered_agent object nullable
  • @type string (default: "ColoradoAgent")
  • name string nullable
  • street_address object nullable
    • @type string (default: "ColoradoAddress")
    • full string nullable
    • street string nullable
    • city string nullable
    • state string nullable
    • zip string nullable
    • country string nullable
  • mailing_address object nullable
    • @type string (default: "ColoradoAddress")
    • full string nullable
    • street string nullable
    • city string nullable
    • state string nullable
    • zip string nullable
    • country string nullable
• url string required

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 ID 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.