/new_hampshire/companies

POST /api/new_hampshire/companies

Price: 5 credits

Get a New Hampshire business's registry record from the Secretary of State QuickStart business database by its Business ID: name, entity type, status, formation dates, jurisdiction, addresses, registered agent, principals (officers/members), NAICS purpose codes, annual report years and contact details.

How to use it

Look up one New Hampshire business by its Business ID (e.g. '259018'). Returns one item with id, name, legal_form (entity type such as 'Domestic Limited Liability Company', 'Foreign Profit Corporation', 'Trade Name'), status, formation_date, citizenship, addresses, registered_agent (name and addresses), principals (officers/members with name, title and address), naics_codes and report years. To find a Business ID by company name, use new_hampshire/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 — New Hampshire Business ID (examples: "259018", "60526", "690759"; minLength: 1)

Response

• @type string (default: "NewHampshireCompany")
• id string required
• name string nullable
• legal_form string nullable
• status string nullable
• corporation_subtype string nullable
• management_style string nullable
• formation_date string nullable
• jurisdiction_formation_date string nullable
• citizenship string nullable
• name_in_jurisdiction string nullable
• duration string nullable
• last_annual_report_year string nullable
• next_report_year string nullable
• expiration_date string nullable
• last_renewal_date string nullable
• fiscal_year_end_date string nullable
• email string nullable
• notification_email string nullable
• phone string nullable
• principal_address string nullable
• mailing_address string nullable
• principal_purpose string nullable
• naics_codes array (default: [])
  • @type string (default: "NewHampshireNaicsCode")
  • code string nullable
  • subcode string nullable
• principals array (default: [])
  • @type string (default: "NewHampshirePrincipal")
  • name string nullable
  • address string nullable
• principal_count integer nullable
• registered_agent object nullable
  • @type string (default: "NewHampshireAgent")
  • name string nullable
  • office_address string nullable
  • mailing_address 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 Business 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.