/maine/companies

POST /api/maine/companies

Price: 1 credit

Get a Maine business entity by its charter number from the Maine Secretary of State business registry: legal name, charter number, legal form, status, filing/qualification date, formation jurisdiction, assumed and former names, principal-office address (physical and mailing) and the clerk/registered agent (name and address).

How to use it

Get one Maine business entity by its charter number (the charter value returned by maine/companies/search). Returns one item with charter, name, legal_form, status, filing_date, jurisdiction, other_names (name, name_type: ASSUMED or FORMER), principal_office (physical, mailing) and registered_agent (name, physical, mailing). Use maine/companies/filings for the entity's filing history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• charter string required — Maine business entity charter number (examples: "20020019LF", "19970467 F", "202400909FC"; minLength: 1)

Response

• @type string (default: "MaineCompany")
• charter string required
• name string required
• legal_form string nullable
• status string nullable
• filing_date string nullable
• jurisdiction string nullable
• other_names array
  • @type string (default: "MaineCompanyOtherName")
  • name string required
  • name_type string required
• principal_office object nullable
  • @type string (default: "MaineCompanyAddress")
  • physical string nullable
  • mailing string nullable
• registered_agent object nullable
  • @type string (default: "MaineCompanyAgent")
  • name string nullable
  • physical string nullable
  • mailing 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 charter 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.