> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration. ## This page - **On-site (HTML):** - **Markdown (.mdx) URL:** ## API base URL and authentication - **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev` - **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route). - **OpenAPI JSON:** ## Recommended docs entrypoints (this site) - [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown). - [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope. - [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`. - [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages. - [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples. - [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths. - [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install. - [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 910 endpoint tools, plus docs_search/docs_read for implementation help. - [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples. - [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start. - [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog. - [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI). - [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls). - [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist. - [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping. - [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages. - [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance. - [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs. - Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract. ## Markdown docs convention - Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`). - Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`). - Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`). --- # Get Yahoo Finance technical insights (https://www.socialfetch.dev/docs/api/v1/yahoo-finance/instruments/symbol/insights/get) ## Summary Get Yahoo Finance technical events, technicals and company snapshot. **Tags:** `Yahoo Finance` ## HTTP - **Method:** GET - **Path:** `/v1/yahoo-finance/instruments/{symbol}/insights` - **Base URL:** `https://api.socialfetch.dev` ## Capability summary - **SDK mapping:** `client.yahooFinance.getInsights({ symbol: "AAPL" })` - **Accepted identifiers:** `symbol` (path) - **Pagination:** none - **Business outcome field:** `data.lookupStatus` with values `found`, `not_found` ## Credits - **Base:** 1 credit per successful lookup. - **Maximum on success (200):** 1 credit. - **Failed requests (`lookup_failed`, `503`):** not charged. - **Authoritative field:** `meta.creditsCharged`. ## Authentication - **`x-api-key`**: API key (`sfk_...`) ## Parameters ### `symbol` (path) - **Required:** yes - **Constraints:** type `string`; minLength: 1; maxLength: 40; pattern: `^[A-Za-z0-9^=.-]+$` - **Description:** Ticker symbol, case-insensitive, e.g. `AAPL`, `^GSPC`, `EURUSD=X`, `BTC-USD`, `7203.T`. ## Responses (status codes) - **200**: Yahoo Finance technical insights. - **400**: Invalid request - **401**: Missing or invalid API key - **402**: Insufficient credits - **500**: Unexpected or billing error - **502**: Lookup could not be completed. - **503**: Service temporarily unavailable; safe to retry with backoff. ## Response body (200) Yahoo Finance technical insights. ### Field outline - **data** (required) — type `object`. Endpoint-specific response payload. - **lookupStatus** (required) — type `string`; enum: found, not_found. Whether the entity was found. HTTP 200 for both outcomes; branch on this field. - **symbol** (required) — type `string`. Ticker symbol the insights are for. - **insights** (required) — type `object`; nullable. Technical events, key technicals, valuation, company snapshot, recommendation, research reports, SEC reports and significant developments. - **meta** (required) — type `object`. Metadata describing the request and billing outcome. - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call. - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request. - **version** (required) — type `string`; enum: v1. Public API version that served the response. ### Example JSON (found) ```json { "data": { "lookupStatus": "found", "symbol": "AAPL", "insights": { "symbol": "AAPL", "instrumentInfo": { "technicalEvents": { "provider": "Trading Central", "sector": "Technology", "shortTermOutlook": { "stateDescription": "Recent bearish events outweigh bullish events.", "direction": "Bearish", "score": 4, "scoreDescription": "Very Strong Bearish Evidence", "sectorDirection": "Bearish", "sectorScore": 3, "sectorScoreDescription": "Strong Bearish Evidence", "indexDirection": "Bearish", "indexScore": 4, "indexScoreDescription": "Very Strong Bearish Evidence" }, "intermediateTermOutlook": { "stateDescription": "Recent bearish events outweigh bullish events.", "direction": "Bearish", "score": 1, "scoreDescription": "Weak Bearish Evidence", "sectorDirection": "Bearish", "sectorScore": 4, "sectorScoreDescription": "Very Strong Bearish Evidence", "indexDirection": "Bearish", "indexScore": 4, "indexScoreDescription": "Very Strong Bearish Evidence" }, "longTermOutlook": { "stateDescription": "There are no events.", "direction": "Neutral", "score": 0, "scoreDescription": "No Evidence", "sectorDirection": "Bullish", "sectorScore": 1, "sectorScoreDescription": "Weak Bullish Evidence", "indexDirection": "Neutral", "indexScore": 0, "indexScoreDescription": "No Evidence" } }, "keyTechnicals": { "provider": "Trading Central", "support": 255.65, "resistance": 333.26, "stopLoss": 306.404578 }, "valuation": { "color": 0, "description": "Overvalued", "discount": "-8%", "relativeValue": "Premium", "provider": "Trading Central" } }, "companySnapshot": { "sectorInfo": "Technology", "company": { "innovativeness": 0.9981, "hiring": 0.9512999999999999, "sustainability": 0.16519999999999999, "insiderSentiments": 0.12390000000000001, "earningsReports": 0.8687999999999999, "dividends": 0.0617 }, "sector": { "innovativeness": 0.5, "hiring": 0.5, "sustainability": 0.5, "insiderSentiments": 0.5, "earningsReports": 0.5, "dividends": 0.5 } }, "recommendation": { "targetPrice": 400, "provider": "Argus Research", "rating": "BUY" }, "events": [ { "eventType": "Price Crosses Moving Average", "pricePeriod": "D", "tradingHorizon": "I", "tradeType": "S", "imageUrl": "https://s.yimg.com/uc/fin/img/assets/generic.svg", "startDate": "2026-11-03T14:30:00.000Z", "endDate": "2026-11-03T14:30:00.000Z" } ], "reports": [ { "id": "ARGUS_2660_AnalystReport_1793708046000", "headHtml": "Analyst Report: Apple Inc", "provider": "Argus Research", "reportDate": "2026-11-03T12:14:06Z", "reportTitle": "Apple manufactures smartphones, tablets, PCs, software, and peripherals for a worldwide customer base. Its products include Mac desktop and mobile PCs, iPhone,…", "reportType": "Analyst Report", "tickers": [ "AAPL" ], "title": "CEO Ternus takes over; raising target to $400" } ], "sigDevs": [ { "headline": "Cnmc Launches Disciplinary Proceedings Against Apple And Amazon", "date": "2026-11-03" } ], "secReports": [ { "id": "0000320193-26-000026_320193", "type": "Periodic Financial Reports", "title": "10-K : Periodic Financial Reports", "description": "Annual report pursuant to Section 13 and 15(d)", "filingDate": "2026-11-03T00:00:00.000Z", "snapshotUrl": "https://cdn.yahoofinance.com/prod/sec-reports-thumbnails/0000320193/000032019326000026/thumbnail.png", "edgarUrl": "https://finance.yahoo.com/sec-filing/AAPL/0000320193-26-000026_320193", "formType": "10-K", "exhibits": [ { "type": "10-K", "url": "https://cdn.yahoofinance.com/prod/sec-filings/0000320193/000032019326000026/aapl-20260926.htm" } ] } ] } }, "meta": { "requestId": "req_yahoo_finance_example", "creditsCharged": 1, "version": "v1" } } ``` ### Machine-readable error codes When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime): - `bad_request` ## Error handling & retries Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status. - **400**: Invalid request **Retry:** Fix the request; retrying the same invalid payload will not help. - **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help. - **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help). - **500**: Unexpected or billing error - **502**: Lookup could not be completed. **Retry:** May be transient; a few retries with backoff are reasonable. - **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter. ### Suggested client defaults - Send the API key using the `x-api-key` header on every request. - On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user. - On `402`, surface an actionable billing message rather than blind retries. ## Examples ### TypeScript SDK ```typescript import { SocialFetchClient } from "@socialfetch/sdk"; const client = new SocialFetchClient({ apiKey: process.env.SOCIALFETCH_API_KEY!, }); const result = await client.yahooFinance.getInsights({ symbol: "AAPL", }); if (!result.ok) { console.error(result.error); } else { console.log(result.value.data); } ``` ### Node.js ```javascript const response = await fetch( "https://api.socialfetch.dev/v1/yahoo-finance/instruments/AAPL/insights", { headers: { "x-api-key": "YOUR_API_KEY" } } ); const data = await response.json(); console.log(data); ``` ### cURL ```bash curl "https://api.socialfetch.dev/v1/yahoo-finance/instruments/AAPL/insights" \ -H "x-api-key: YOUR_API_KEY" ``` ### Python ```python import requests response = requests.get( "https://api.socialfetch.dev/v1/yahoo-finance/instruments/AAPL/insights", headers={"x-api-key": "YOUR_API_KEY"}, ) data = response.json() print(data) ```