/dc/companies/agents

POST /api/dc/companies/agents

Price: 1 credit

List the registered agent history of a Washington DC business entity from the DLCP CorpOnline registry by Initial File No. or business GUID: every recorded registered agent with the filing that appointed it, its effective start date and its street address.

How to use it

List the registered agent history of one Washington DC business entity by its Initial File No. (e.g. '963942') or business GUID. Returns one item per agent record with name, filing_number, effective_start_date, filing_date (ISO YYYY-MM-DD) and address. Entities whose agent was never recorded through a filing return an empty list; the current agent is always available on dc/companies.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Business GUID or Initial File No. of the entity (examples: "963942", "26089d85-68f5-43c1-9464-0f380c0ccd85"; minLength: 1)
• count integer required — Max number of agent records to return (min: 1)

Response

• @type string (default: "DcCompanyAgent")
• name string required
• filing_number string nullable
• effective_start_date string nullable
• filing_date string nullable
• address object nullable
  • @type string (default: "DcAddress")
  • street string nullable
  • street2 string nullable
  • city string nullable
  • state string nullable
  • province string nullable
  • zip string nullable
  • postal_code string nullable
  • country string nullable
  • county string nullable
  • full 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 (well-formed but unknown Initial File No. or GUID) 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.