/north_dakota/companies

POST /api/north_dakota/companies

Price: 1 credit

Get full North Dakota business details from the Secretary of State registry by system id: name, filing type and subtype, status, standings (annual report, registered agent, other), jurisdiction of formation, nature of business, term of duration, initial filing date, delayed effective date, expiration date, annual report due date, owner (name, address), principal and mailing addresses and registered agent (name, type, address).

How to use it

Get one North Dakota business from the Secretary of State registry by system id (the public 10-digit SOS control id). Returns one item with system_id, name, filing_type, filing_subtype (e.g. Engaged in Farming), status, standing_ar / standing_ra / standing_other, formed_in (jurisdiction of formation), nature_of_business (set on trade names), duration, initial_filing_date, delayed_effective_date, expiration_date (set when duration is not perpetual), annual_report_due_date, owner_name and owner_address (the owner of a trade name), principal_address (street/locality), mailing_address and registered_agent (name/type/address). To find a system id by name, use north_dakota/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• system_id string required — North Dakota business system id (examples: "0000028476", "28476"; minLength: 1)

Response

• @type string (default: "NorthDakotaCompany")
• system_id string required
• name string nullable
• filing_type string nullable
• filing_subtype string nullable
• status string nullable
• standing_ar string nullable
• standing_ra string nullable
• standing_other string nullable
• formed_in string nullable
• nature_of_business string nullable
• duration string nullable
• initial_filing_date string nullable
• delayed_effective_date string nullable
• expiration_date string nullable
• inactive_date string nullable
• annual_report_due_date string nullable
• owner_name string nullable
• owner_address string nullable
• principal_address object nullable
  • @type string (default: "NorthDakotaAddress")
  • street string nullable
  • locality string nullable
• mailing_address object nullable
  • @type string (default: "NorthDakotaAddress")
  • street string nullable
  • locality string nullable
• registered_agent object nullable
  • @type string (default: "NorthDakotaRegisteredAgent")
  • name string nullable
  • type string nullable
  • address 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 system 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.

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.