POST /api/new_york/companies
Price: 1 credit
Get a New York business entity by its DOS ID from the NY Department of State Corporation & Business Entity Database: legal name, foreign legal name, fictitious name, entity type and status, reason for status, section of law, duration date, jurisdiction, county, statement status and next-statement due date, initial DOS filing date, effective and foreign-formation dates, inactive and dissolution dates, registered agent (name + address), chief executive officer (name + address), principal executive office address, service-of-process recipient and stock/share classes.
Get one New York business entity by its DOS ID (numeric). Returns one item with dos_id, name, foreign_legal_name, fictitious_name, company_type, entity_status (Active/Inactive), reason_for_status, section_of_law, duration_date, jurisdiction, county, nfp_category, statement_status, initial_dos_filing_date, effective_initial_filing_date, foreign_formation_date, inactive_date, next_statement_due_date, latest_dissolution_date, electronic_service_of_process_status, is_farm_corporation, registered_agent (name, address), ceo (name, address), principal_executive_office_address, service_of_process (name, address) and stock_shares (list of stock_type, par_value, quantity). Dates are ISO YYYY-MM-DD. NY publishes the CEO but not a full officers/directors roster. Use new_york/companies/search to find the DOS ID by name.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)dos_id string required — New York DOS ID (numeric entity identifier) (examples: "1453447", "1767613"; minLength: 1)@type string (default: "NewYorkCompany")dos_id string requiredname string requiredforeign_legal_name string nullablefictitious_name string nullablecompany_type string nullableentity_status string nullablereason_for_status string nullablesection_of_law string nullableduration_date string nullablejurisdiction string nullablecounty string nullablenfp_category string nullablestatement_status string nullableinitial_dos_filing_date string nullableeffective_initial_filing_date string nullableforeign_formation_date string nullableinactive_date string nullablenext_statement_due_date string nullablelatest_dissolution_date string nullableelectronic_service_of_process_status string nullableis_farm_corporation boolean nullableregistered_agent object nullable@type string (default: "NewYorkContact")name string nullableaddress object nullable@type string (default: "NewYorkAddress")street string nullablecity string nullablestate string nullablezip string nullablecountry string nullableceo object nullable@type string (default: "NewYorkContact")name string nullableaddress object nullable@type string (default: "NewYorkAddress")street string nullablecity string nullablestate string nullablezip string nullablecountry string nullableprincipal_executive_office_address object nullable@type string (default: "NewYorkAddress")street string nullablecity string nullablestate string nullablezip string nullablecountry string nullableservice_of_process object nullable@type string (default: "NewYorkContact")name string nullableaddress object nullable@type string (default: "NewYorkAddress")street string nullablecity string nullablestate string nullablezip string nullablecountry string nullablestock_shares array (default: [])@type string (default: "NewYorkStockShare")stock_type string nullablepar_value string nullablequantity integer nullable422 — 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 DOS ID) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.