/california/companies/filings

POST /api/california/companies/filings

Price: 1 credit

Get the filing history of a California business entity from the Secretary of State bizfile registry by entity number: filing type, control id, filing and effective dates, a link to the scanned filing document when one is published, and registry notes attached to the filing.

How to use it

Get the filing history of one California business entity by its Secretary of State entity number. Returns a list of filings, newest first, each with amendment_id, filing_type (Initial Filing, Statement of Information, Termination, System Amendment, ...), control_id, filing_date and effective_date (YYYY-MM-DD), document_url (a PDF of the scanned filing, present only for filings whose image is published) and notes. A note carries the registry field it touches (field_name, display_name) with its previous value (changed_from) and new value (changed_to); a filing that sets a value for the first time has no changed_from. Entities whose amendments are all withheld from public history return an empty list.

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 — California business entity number (examples: "0806592", "201727810678"; minLength: 1)
• count integer required — Max number of filings to return (min: 1)

Response

• @type string (default: "CaliforniaFiling")
• amendment_id integer required
• filing_type string nullable
• control_id string nullable
• filing_date string nullable
• effective_date string nullable
• document_url string nullable
• notes array (default: [])
  • @type string (default: "CaliforniaFilingNote")
  • changed_from string nullable
  • changed_to string nullable
  • field_name string nullable
  • display_name 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 California business entity exists with this entity 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.