/florida/companies

POST /api/florida/companies

Price: 1 credit

Get a Florida business's registry record from the Division of Corporations (Sunbiz) by its Document Number: exact name, entity type, FEI/EIN, date filed, jurisdiction, status, last event, principal and mailing addresses, registered agent (name and address), officers/directors (title, name, address), annual reports (year and filed date) and the event/filing history (type, dates, description).

How to use it

Look up one Florida business by its Document Number (e.g. '849374', 'L20000394839'). Returns one item with document_number, name, legal_form, fei_ein, date_filed, state (jurisdiction of formation), status, last_event, principal_address, mailing_address, registered_agent, officers (title, name, address), annual_reports and events (the filing/event history). To find a Document Number by company name, use florida/companies/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• document_number string required — Florida business Document Number (optional single leading letter + digits) (examples: "849374", "L20000394839", "F96000005067"; minLength: 1)

Response

• @type string (default: "FloridaCompany")
• document_number string required
• name string nullable
• legal_form string nullable
• fei_ein string nullable
• date_filed string nullable
• state string nullable
• status string nullable
• last_event string nullable
• last_event_at string nullable
• last_event_effective_at string nullable
• principal_address object nullable
  • @type string (default: "FloridaAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • changed_at string nullable
• mailing_address object nullable
  • @type string (default: "FloridaAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • changed_at string nullable
• registered_agent object nullable
  • @type string (default: "FloridaAgent")
  • name string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
  • name_changed_at string nullable
  • address_changed_at string nullable
• officers array (default: [])
  • @type string (default: "FloridaOfficer")
  • name string nullable
  • document_number string nullable
  • street string nullable
  • city string nullable
  • state string nullable
  • zip string nullable
  • country string nullable
• annual_reports array (default: [])
  • @type string (default: "FloridaAnnualReport")
  • year string nullable
  • filed_at string nullable
• events array (default: [])
  • @type string (default: "FloridaEvent")
  • type string nullable
  • filed_at string nullable
  • effective_at string nullable
  • description string nullable
• url string required

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 business found for the given Document 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.