POST /api/idaho/companies
Price: 1 credit
Get full Idaho business details from the Secretary of State registry by file number: name, filing type, status, standing, jurisdiction of formation, term of duration, initial filing date, inactive filing date, expiration date, annual report due date, principal and mailing addresses and registered agent (name, type, registration id, address).
Get one Idaho business from the Secretary of State registry by file number. Returns one item with file_number, name (legal name is only present for foreign entities; for Idaho-domestic entities the registry detail omits the name — use idaho/companies/search to obtain it), filing_type, status, standing, formed_in (jurisdiction of formation), duration, initial_filing_date, inactive_filing_date (set when the entity is no longer active), expiration_date (set when duration is not perpetual), annual_report_due_date, principal_address (street/locality), mailing_address and registered_agent (name/type/registration_id/address). To check whether a file number exists, use idaho/companies/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)file_number string required — Idaho business file number (examples: "295132", "530860"; minLength: 1)@type string (default: "IdahoCompany")file_number string requiredname string nullablefiling_type string nullablestatus string nullablestanding string nullableformed_in string nullableduration string nullableinitial_filing_date string nullableinactive_filing_date string nullableexpiration_date string nullableannual_report_due_date string nullableprincipal_address object nullable@type string (default: "IdahoAddress")street string nullablelocality string nullablemailing_address object nullable@type string (default: "IdahoAddress")street string nullablelocality string nullableregistered_agent object nullable@type string (default: "IdahoRegisteredAgent")name string nullabletype string nullableregistration_id string nullableaddress string 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 — The entity was not found, or a precondition failed 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.