/california/companies

POST /api/california/companies

Price: 1 credit

Get full California business entity details from the Secretary of State bizfile registry by entity number: name, entity type, status, SOS/FTB/agent/VCFCF standings, jurisdiction of formation, initial filing date, inactive date, Statement of Information due date, principal and mailing addresses and registered agent with its authorized employees.

How to use it

Get one California business entity by its Secretary of State entity number (7-digit corporation number such as 0806592, 12-digit LLC/LP number such as 201727810678, or a letter-prefixed number such as B20260033420; a leading 'C' is stripped automatically). Returns one item with file_number, internal_id, name, foreign_name, entity_subtype, status, standing_sos, standing_ftb, standing_agent, standing_vcfcf, formed_in, initial_filing_date, inactive_date and statement_of_info_due_date (all YYYY-MM-DD), principal_address, mailing_address, registered_agent (with employees) and is_publicly_traded. Use california/companies/search to find an entity number by name, california/companies/filings for the filing history and california/companies/disclosures for publicly traded disclosure data.

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", "B20260033420"; minLength: 1)

Response

• @type string (default: "CaliforniaCompany")
• file_number string required
• internal_id integer required
• name string nullable
• foreign_name string nullable
• entity_subtype string nullable
• status string nullable
• standing_sos string nullable
• standing_ftb string nullable
• standing_agent string nullable
• standing_vcfcf string nullable
• formed_in string nullable
• initial_filing_date string nullable
• inactive_date string nullable
• statement_of_info_due_date string nullable
• principal_address object nullable
  • @type string (default: "CaliforniaAddress")
  • street string nullable
  • locality string nullable
• mailing_address object nullable
  • @type string (default: "CaliforniaAddress")
  • street string nullable
  • locality string nullable
• registered_agent object nullable
  • @type string (default: "CaliforniaRegisteredAgent")
  • name string nullable
  • agent_type string nullable
  • address string nullable
  • employees array (default: [])
    • @type string (default: "CaliforniaAgentEmployee")
    • name string required
    • address string nullable
• is_publicly_traded boolean (default: false)
• can_file_statement_of_info boolean (default: false)
• can_reinstate boolean (default: false)

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.