/south_carolina/companies

POST /api/south_carolina/companies

Price: 5 credits

Get a South Carolina business entity by its GUID from the Secretary of State Business Entities Online registry: legal name, entity id, entity type, status, domestic/foreign, jurisdiction, effective / expiration / term end / dissolved dates, registered agent (name, address), assumed names and former names. Obtain the guid from south_carolina/companies/search.

How to use it

Get one South Carolina business entity by its guid (find it with south_carolina/companies/search). Returns one item with name, entity_id (the public entity number, e.g. 00065806), legal_form (e.g. Corporation, Limited Liability Company, Limited Partnership), status (e.g. Good Standing, Dissolved, Forfeited), domestic_foreign (Domestic or Foreign), jurisdiction (state of incorporation), effective_date, expiration_date, term_end_date, dissolved_date (M/D/YYYY, set when applicable), registered_agent (name, address), assumed_names (name, effective_date, expiration_date, status) and former_names. Use south_carolina/companies/filings for the entity's filing history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• guid string required — South Carolina entity GUID (obtained from south_carolina/companies/search) (examples: "5cfd981f-7699-443d-9172-0b8be0b3591f", "6b1e32e5-f902-428a-af55-c4adb108d7d5")

Response

• @type string (default: "SouthCarolinaCompany")
• guid string required
• name string required
• entity_id string nullable
• legal_form string nullable
• status string nullable
• domestic_foreign string nullable
• jurisdiction string nullable
• effective_date string nullable
• expiration_date string nullable
• term_end_date string nullable
• dissolved_date string nullable
• registered_agent object nullable
  • @type string (default: "SouthCarolinaRegisteredAgent")
  • name string nullable
  • address string nullable
• assumed_names array
  • @type string (default: "SouthCarolinaAssumedName")
  • name string required
  • effective_date string nullable
  • expiration_date string nullable
  • status string nullable
• former_names array
  • @type string (default: "SouthCarolinaFormerName")
  • name string required
  • filed_at 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 nonexistent 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.