/kentucky/companies

POST /api/kentucky/companies

Price: 10 credits

Get a Kentucky business entity by its control number from the Kentucky Secretary of State business registry: organization number, legal name, profit/non-profit, company type, industry, employee band, county, status, standing, formation state, file/authority/organization/expiration dates, last annual report date, share count, principal-office address, registered agent, and the entity's current officers, initial officers, assumed names (DBAs) and former names.

How to use it

Get one Kentucky business entity by its control number (the ctr value returned by kentucky/companies/search). Returns one item with ctr, organization_number, name, is_profit, company_type, status, standing, state, file_date, authority_date/organization_date, last_annual_report_date, principal_office, registered_agent, current_officers and initial_officers (title, name), assumed_names (name, status, expiration_date) and former_names (name, action). Use kentucky/companies/activities and kentucky/companies/documents for the filing history and document images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ctr string required — Kentucky business entity control number (the ctr identifier from a search result) (examples: "978159", "200788", "283237"; minLength: 1)

Response

• @type string (default: "KentuckyCompany")
• ctr string required
• organization_number string nullable
• name string required
• is_profit boolean nullable
• company_type string nullable
• industry string nullable
• employee_count string nullable
• county string nullable
• status string nullable
• standing string nullable
• state string nullable
• file_date string nullable
• authority_date string nullable
• organization_date string nullable
• expiration_date string nullable
• last_annual_report_date string nullable
• share_count string nullable
• principal_office string nullable
• registered_agent string nullable
• applicant_address string nullable
• current_officers array
  • @type string (default: "KentuckyOfficer")
  • name string nullable
• initial_officers array
  • @type string (default: "KentuckyOfficer")
  • name string nullable
• assumed_names array
  • @type string (default: "KentuckyAssumedName")
  • name string nullable
  • status string nullable
  • expiration_date string nullable
• former_names array
  • @type string (default: "KentuckyFormerName")
  • name string nullable
  • action string nullable
  • related_ctr 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 (no entity exists for this control 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.