Stock Price Application

Stock Price Application

Article Type: Feature / Configuration Audience: Solution Architects, Application Designers, Partners Module: Fuuz Platform / Bootcamp Sessions → Session 1 Stock Prices Applies to Versions: 2025.11+

Overview

The Stock Price Application retrieves grouped daily OHLC data (open, high, low, close), volume, VWAP, and transaction counts for all U.S. symbols for the previous trading day, then persists those aggregates to the StockPrice data model for reporting and analysis.

Note: Data Change Capture is enabled on the model with a retention period of 120 days.

Note: The original KB article includes an attachment (StockPriceApplication001.zip) containing the application package. Download it from the original article; the file must be re-attached/linked in this repo.

Architecture & Data Flow

Components

• Manifest & Versions: Name = Stock Price Application; Version = 0.0.1; specVersion = 2.0.0; platformVersion = 2025.11.2.
• Connection: MassiveStockPriceAPI base URL Open Massive API (Authorization: Bearer token).
• Screen Route: /bootcampSessions/session1StockPrices/stockPrices (menu accessible).

Important: The HTTP path is /v2/aggs/grouped/locale/us/market/stocks/{date}?adjusted=true, where date is computed by $moment().subtract(1, 'day').format("YYYY-MM-DD").

Flow Nodes

1. Schedule: Triggers the job on your chosen cadence (e.g., daily).
2. Transform: Computes yesterday's date via $moment().subtract(1, 'day').format("YYYY-MM-DD").
3. Set Context: Stores the computed date in state.context.data.date for downstream nodes.
4. HTTP GET: Calls MassiveStockPriceAPI using the path above and returns grouped aggregates.
5. Mutation: Builds a payload array from the response and executes createStockPrice to persist records.

Configuration Steps

1. Set Connection: Configure MassiveStockPriceAPI with base URL Open Massive API and a valid Bearer token (store securely).
2. Schedule the Flow: Open the Schedule editor and set a daily cadence after market close.
3. Verify the Report: Navigate to /bootcampSessions/session1StockPrices/stockPrices and use filters to validate imported aggregates.

Screen Details

• Route: /bootcampSessions/session1StockPrices/stockPrices
• Filters: Stock (text), Period (date range), Created/Updated At & By, GraphQL Where builder.
• Table Columns: Stock, Transactions, Average Price, Close, High, Low, Open, Volume, Request Id, Period, Created/Updated.

Data Model: StockPrice

Field	Type	Description
id	(unknown)	Primary unique ID.
stock	(unknown)	Exchange symbol (ticker).
transactions	(unknown)	Number of transactions in the aggregate window.
averagePrice	(unknown)	Volume-weighted average price (VWAP).
close	(unknown)	Close price for the period.
high	(unknown)	Highest price for the period.
low	(unknown)	Lowest price for the period.
open	(unknown)	Open price for the period.
volume	(unknown)	Trading volume for the period.
requestId	(unknown)	Upstream request identifier (if provided).
period	(unknown)	Trading date (YYYY-MM-DD).
json	(unknown)	Raw JSON payload (optional).

Retention & Change Capture: Change capture is enabled with 120 days retention for auditing and rollbacks.

Endpoint & Payload Mapping

Response keys from the upstream API are mapped to the StockPrice model fields as follows:

API Key	Model Field	Notes
T	stock	Ticker symbol
vw	averagePrice	Volume-weighted average price
c	close	Close price
h	high	High price
l	low	Low price
o	open	Open price
n	transactions	Number of transactions
v	volume	Volume
(computed)	period	Derived date (YYYY-MM-DD)

The mutation sends an array payload to createStockPrice, inserting a record per symbol for the computed period.

Resources

• Open Massive API

Optional Matrix

Feature	Option A	Option B
Scheduling cadence	✓ Configurable	✗ Not fixed
Connection auth	⚠ Bearer Token	✓ Secret vault supported

Troubleshooting

• HTTP 401/403: Check Authorization header and confirm the MassiveStockPriceAPI connection is active.
• Empty results: Verify the computed date and that the upstream endpoint supports the requested trading day.
• Mutation errors: Confirm GraphQL types and that required fields are present.

Revision History

Version	Date	Editor	Description
1.0	2025-12-24	Fuuz Documentation Team	Initial Release

See Also

• How-to-Create-APIs-Using-Data-Flows-in-Fuuz
• How-to-Setup-a-daily-file-import-using-Fuuz-Data-Flows
• Data-Flow-Nodes-Reference
• Setting-TTL-on-a-Data-Model-Table
• Master-Data-Table-Screen-Design-Standard

---

Source: support.fuuz.com