POST /api/yahoo/finance/profile
Price: 5 credits
Get the company profile of a ticker: business summary, sector, address, officers and SEC filings
Company profile of a stock or fund ticker, with its officers and their pay, governance risk scores and the SEC filings list with exhibit links.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)symbol string required — Ticker symbol (examples: "AAPL", "JPM", "SPY"; minLength: 1; pattern: \S)@type string (default: "YahooFinanceProfile")id string requiredname string nullableshort_name string nullablequote_type string nullableexchange string nullableexchange_name string nullablecurrency string nullabletimezone string nullablefirst_trade_at integer nullabledescription string nullablesector string nullablesector_key string nullableindustry string nullableindustry_key string nullableemployee_count integer nullableaddress string nullablecity string nullablestate string nullablepostal_code string nullablecountry string nullablephone string nullablewebsite string nullableir_website string nullableaudit_risk integer nullableboard_risk integer nullablecompensation_risk integer nullableshareholder_rights_risk integer nullableoverall_risk integer nullablegovernance_at integer nullablecompensation_as_of_at integer nullableofficers array (default: [])@type string (default: "YahooFinanceOfficer")name string requiredtitle string nullableage integer nullablebirth_year integer nullablefiscal_year integer nullabletotal_pay number nullableexercised_value number nullableunexercised_value number nullablefilings array (default: [])@type string (default: "YahooFinanceFiling")form_type string nullabletitle string nullablefiled_at integer nullableurl string nullableexhibits array (default: [])@type string (default: "YahooFinanceFilingExhibit")exhibit_type string nullableurl string requireddownload_url string nullable422 — 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 — Symbol not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.