> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Unusual Whales: Get Stock Info

Get stock fundamentals. Returns market cap, sector, 30-day average volume, beta, next earnings date, options availability, and a short company description. Ideal for: enriching ticker context in workflows, screening by sector or market cap size, checking upcoming earnings dates.

![Unusual Whales: Get Stock Info logo](https://cdn.b3.fun/unusual_whales.png)
Catalog action Blockchain Data

Get stock fundamentals. Returns market cap, sector, 30-day average volume, beta, next earnings date, options availability, and a short company description. Ideal for: enriching ticker context in workflows, screening by sector or market cap size, checking upcoming earnings dates.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `unusualwhales-get-stock-info` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `stock`, `price`, `market-data`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | Yes | Stock ticker symbol \(e.g., 'AAPL', 'TSLA', 'MSFT'\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `stock` | `object` | Yes | - |

## Examples

**Workflow node**

```json
{
  "type": "unusualwhales-get-stock-info",
  "payload": {
    "ticker": "example-ticker"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/unusualwhales-get-stock-info/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "ticker": "example-ticker"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.