/delaware/companies

POST /api/delaware/companies

Price: 5 credits

Get a Delaware business entity by its file number from the Delaware Division of Corporations registry: file number, entity name, legal form (Corporation, Limited Liability Company, Limited Partnership, ...), entity subtype (General, Statutory Trust, ...), residency (Domestic/Foreign), formation jurisdiction, incorporation/formation date, and the registered agent (name, address, city, county, state, postal code, phone).

How to use it

Get one Delaware business entity by its file number (the file_number returned by delaware/companies/search). Returns one item with file_number, name, legal_form, entity_subtype, residency, state, incorporation_date and registered_agent (name, address, city, county, state, postal_code, phone).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• file_number string required — Delaware business entity file number (examples: "732109", "6649915", "3894712"; minLength: 1)

Response

• @type string (default: "DelawareCompany")
• file_number string required
• name string required
• legal_form string nullable
• entity_subtype string nullable
• residency string nullable
• state string nullable
• incorporation_date string nullable
• registered_agent object nullable
  • @type string (default: "DelawareRegisteredAgent")
  • name string nullable
  • address string nullable
  • city string nullable
  • county string nullable
  • state string nullable
  • postal_code string nullable
  • phone 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 file 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.