Back to Tester

Data Flow Mapping

This page visualizes how data from the ICIS API is fetched and mapped for each tab in the application.

1. Filter Population
The app calls internal API routes which in turn fetch data from ICIS API endpoints to populate filter dropdowns.

Markets

APP: /api/markets

ICIS: /markets

Products (Specifications)

APP: /api/products

ICIS: /priceAssessments/specifications

Periods

APP: /api/periods

ICIS: /periods

2. Main Data Fetch
When filters are applied, the app calls an internal route which fetches the main dataset from the ICIS API.

Fetch Data

APP: /api/prices

ICIS: /priceAssessments

3. Data Mapping
The JSON response (containing `data` and `included` arrays) is mapped to the table columns.
item.attributes.createdForDate
to
date
item.attributes.midpoint
to
price
included[currency].attributes.code
to
currency
included[market].attributes.name
to
market
included[unit].attributes.symbol
to
unit