Ferro Chrome (FE-CR) - Per Troy Ounce Historical Price API with OHLC and volume endpoints

Metals-API 9 min read
Ferro Chrome (FE-CR) - Per Troy Ounce Historical Price API with OHLC and volume endpoints

Symbol: Ferro Chrome (FE-CR) →

You need historical Ferro Chrome (FE-CR) pricing per troy ounce to backfill charts, run risk analytics, or price contracts—and you also want daily OHLC to build candlesticks. By the end of this guide, you’ll be able to pull latest and historical FE-CR in USD/oz and oz/USD, request daily OHLC for a given date, and handle units, caching, and non-trading days correctly.

What you can build with FE-CR per-troy-ounce data

Common workflows include:

Illustration: Ferro Chrome (FE-CR) - Per Troy Ounce Historical Price API with OHLC and volume endpoints
  • Backfilling a FE-CR time series for technical indicators (SMA, RSI, Bollinger) and risk models (VaR backtests).
  • Rendering candlestick charts from OHLC, with USD/oz on the y-axis.
  • Converting between oz, g, kg, and metric tons for procurement and manufacturing pricing.
  • Alerting on day-over-day percentage moves or intraday crosses in dashboards.

Metals-API delivers FE-CR data as JSON over simple REST endpoints, with the base currency defaulting to USD. Explore the full capabilities in the Documentation, and confirm symbols on the Symbols page.

Key endpoints to integrate for FE-CR

We’ll focus on three endpoints that cover most charting and analytics use cases:

  • Latest Rates: get current FE-CR in oz/USD and USD/oz.
  • Time-Series: daily closes for a date range (backfill or refresh).
  • OHLC: open, high, low, close for a specific date (candlestick).

Note: Volume availability varies by symbol and plan; check the Documentation for the latest support details. Metals-API does not offer a free trial. A dedicated Copper Monthly plan exists at $19.99/mo; for FE-CR and other symbols, select the plan that matches your throughput and data needs.

Understanding units and base currency (don’t get tripped up)

Metals-API responses are denominated with base=USD by default. That means:

  • rates.FE-CR = troy ounces of FE-CR per 1 USD (oz/USD).
  • rates.USDFE-CR = USD per 1 troy ounce of FE-CR (USD/oz).

This inversion is crucial for charting and pricing. For UI displays and most risk models, you likely want USD per ounce (USD/oz), which is the USDFE-CR rate. If you only receive FE-CR (oz/USD), invert it: USD/oz = 1 / (oz/USD). A troy ounce is 31.1034768 grams; multiply USD/oz by 32.1507466 to get USD/kg, and by 32150.7466 for USD/metric ton.

Latest FE-CR: curl request and official response

Request FE-CR together with its USD/oz inverse in one call. Replace YOUR_API_KEY with your key.

curl "https://metals-api.com/api/latest?access_key=YOUR_API_KEY&symbols=FE-CR,USDFE-CR"

Official response (copy-pasteable for local testing):

{"success":true,"timestamp":1793750880,"date":"2026-11-04","base":"USD","rates":{"FE-CR":7.8828648659206,"USD":1,"USDFE-CR":0.12685743279999956}}

What you’ll actually use from this payload:

  • timestamp and date: for caching and UI last-updated labels (timestamps are UTC).
  • rates.FE-CR (oz/USD): primarily if you need quantity-per-dollar conversions.
  • rates.USDFE-CR (USD/oz): this is typically what you chart or quote in apps.

Parse FE-CR latest in JavaScript and convert to kg and metric ton

async function fetchLatestFECR() {
  const url = "https://metals-api.com/api/latest?access_key=YOUR_API_KEY&symbols=FE-CR,USDFE-CR";
  const res = await fetch(url);
  if (!res.ok) throw new Error(`HTTP ${res.status}`);
  const data = await res.json();

  // Validate success and required fields
  if (!data.success || !data.rates || data.rates.USDFE-CR == null) {
    throw new Error("Missing FE-CR rates in response.");
  }

  const usdPerOz = data.rates["USDFE-CR"];    // USD per troy ounce
  const ozPerUsd = data.rates["FE-CR"];       // troy ounces per USD
  const ts = data.timestamp;                  // Unix timestamp (UTC seconds)

  // Unit conversions
  const OUNCES_PER_KG = 35.27396195;          // avoirdupois; for metals pricing, convert via troy ounce
  const TROY_OUNCES_PER_KG = 32.1507466;      // precise kg conversion for troy ounces
  const usdPerKg = usdPerOz * TROY_OUNCES_PER_KG;
  const usdPerMetricTon = usdPerKg * 1000;

  return {
    date: data.date,
    timestamp: ts,
    usdPerOz,
    ozPerUsd,
    usdPerKg,
    usdPerMetricTon
  };
}

fetchLatestFECR()
  .then(prices => {
    console.log("FE-CR latest:", prices);
  })
  .catch(err => {
    console.error("Failed to fetch FE-CR:", err);
  });

Production tips:

  • Cache by timestamp to avoid re-polling unchanged data within your plan’s update interval.
  • Display the date/time as UTC in the UI to match the API clock.
  • Guard for missing fields (e.g., if you request only FE-CR and not USDFE-CR, compute USD/oz with 1 / rates["FE-CR"]).

Historical and time-series FE-CR for charts and backfills

For chart backfills and analytics windows (e.g., 252 trading days), request the time-series endpoint. It returns daily rates keyed by ISO date. Keep it simple by asking for both FE-CR and its inverse so you don’t invert client-side:

curl "https://metals-api.com/api/timeseries?access_key=YOUR_API_KEY&start_date=2026-01-01&end_date=2026-11-04&symbols=FE-CR,USDFE-CR"

Response structure includes:

  • timeseries: boolean
  • start_date, end_date
  • base: typically USD
  • rates: daily objects keyed by date, each containing FE-CR and/or USDFE-CR

Practical guidance:

  • Weekends and holidays: some days may be absent or carry forward the last available close. Handle gaps when computing rolling indicators.
  • Pagination: if your requested span exceeds limits for your plan, split the range into multiple calls and merge by date on the client or in your ETL.
  • Normalize to USD/oz early in your pipeline so indicators and chart axes use the same units across all views.

Daily OHLC for FE-CR candlesticks

Use the OHLC endpoint to fetch the open, high, low, and close for a given date. This is ideal for daily candles and range analysis. The endpoint follows this pattern:

curl "https://metals-api.com/api/open-high-low-close/2026-11-04?access_key=YOUR_API_KEY&symbols=FE-CR,USDFE-CR"

Notes:

  • Request USDFE-CR to receive the USD/oz OHLC directly. If you only request FE-CR (oz/USD), invert in your charting layer.
  • If a date falls on a weekend/holiday, the service may return the most recent available session values; check the returned date and timestamp fields before plotting.
  • Availability of OHLC can depend on your plan and symbol—verify FE-CR support in the Documentation.

Conversion: quote FE-CR quantities in USD without manual math

When pricing conversions (e.g., how much USD for 500 oz of FE-CR), you can either multiply by USDFE-CR from latest/time-series, or use the convert endpoint. For example:

curl "https://metals-api.com/api/convert?access_key=YOUR_API_KEY&from=FE-CR&to=USD&amount=500"

This returns the USD notional for 500 troy ounces of FE-CR using the current rate. For bulk procurement, convert to kilograms or metric tons as needed on your side using the troy ounce conversions above.

Data hygiene and performance patterns that save time

  • Base and inversion: Prefer requesting both FE-CR and USDFE-CR. It removes client-side inversions and rounding drift.
  • Timezones: Treat timestamps as UTC. Convert once at your API gateway or ETL step for regional dashboards.
  • Caching: Cache by the API timestamp. If timestamps don’t change between polls, don’t recompute indicators or republish charts.
  • Weekend/holiday handling: Expect flat sessions or gaps. If your chart library expects uniform spacing, pre-fill missing days with the prior close and a volume of zero (if volume is part of your model).
  • Outliers and splits: Metals don’t have stock-like splits, but outliers occur on thin sessions. Winsorize or median-smooth before triggering alerts.
  • Unit normalization: Use a single canonical unit (USD/oz) for storage. Derive USD/kg and USD/metric ton on read to maintain consistency.

Symbol verification and plan selection

Confirm FE-CR and any related inverses on the Metals-API Supported Symbols page. For throughput, latency, and endpoint access (including OHLC), evaluate plans in the MCP portal and pick the tier that matches your update interval and historical depth. There is no free trial; get an API key to start testing against your workloads.

Integrating FE-CR into pricing and analytics stacks

Common target systems and patterns:

  • Trading tools and backtesters: Pull time-series USDFE-CR, compute indicators, cache to a time-series database (e.g., TimescaleDB or InfluxDB), and render via your charting library.
  • E-commerce/ERP pricing: Cache latest USDFE-CR, compute USD/kg or USD/metric ton centrally, and propagate to SKUs via your pricing microservice.
  • Risk and P&L: Snapshot USDFE-CR at intervals for mark-to-market, using the same inversion logic across instruments to avoid basis inconsistencies.

For more endpoint details (historical, fluctuation, bid/ask, intraday, and WebSocket streaming), see the Metals-API Documentation.

Notes on volume and OHLC completeness

Volume is not universally available for every metal and venue. If your candlestick model depends on volume, design your charting to:

  • Plot OHLC even when volume is missing.
  • Fallback to tick count or session duration proxies only if they’re clearly labeled.
  • Handle zero-volume days explicitly to avoid misleading moving averages.

Check the symbol-specific documentation and your plan entitlements to understand which FE-CR datapoints are present for OHLC and whether volume fields are exposed.

Reliability, governance, and data lineage

For production systems, log the raw JSON payloads, store the timestamp and date alongside computed USD/oz and unit conversions, and version any transformation logic (e.g., rounding rules). If an upstream revision occurs, you can reproduce downstream analytics from raw events. Consider a circuit-breaker that freezes prices on stale timestamps and sends an alert rather than ingesting duplicates.

Creative applications: fusing FE-CR with broader industrial insights

Teams often fuse FE-CR pricing with macro or supply-side data for context:

  • Combine USDFE-CR with energy indices to model smelting cost sensitivities.
  • For manufacturing forecasts, correlate FE-CR with steel grades it influences and track procurement lead times.
  • When exploring rare-earth and alloy dynamics, consider adding neodymium (ND) and other industrial metals as complementary datasets (verify symbols first). This is where digital transformation meets practical procurement—automated, data-driven decisions across your stack.

For additional reference data and context, consult sources like the London Metal Exchange and USGS Minerals Information when building research dashboards.

Quick checklist before you ship

  • Request both FE-CR and USDFE-CR so you have oz/USD and USD/oz in a single payload.
  • Normalize to USD/oz for storage; derive other units on read.
  • Cache by API timestamp; don’t recompute when unchanged.
  • Design for weekend/holiday gaps and potential carry-forward closes.
  • Log raw responses for audit; tag computed fields with source timestamp and date.

FAQ

Q: What’s the difference between FE-CR and USDFE-CR?
A: FE-CR is troy ounces per 1 USD (oz/USD). USDFE-CR is USD per 1 troy ounce (USD/oz). For charts and pricing, USDFE-CR is usually the field you want.

Q: How do I convert USD/oz to USD/kg or USD/metric ton?
A: Multiply USD/oz by 32.1507466 for USD/kg, and then by 1000 for USD/metric ton. These use troy-ounce conversions.

Q: Why is the same value being returned across a weekend?
A: On non-trading days and holidays, the rate may carry forward from the last session. Handle gaps or repeats in your time-series logic accordingly.

Q: Can I get FE-CR OHLC for a specific date?
A: Yes—use the open-high-low-close/YYYY-MM-DD endpoint and include symbols=FE-CR,USDFE-CR. Availability for specific symbols and fields may depend on plan and data coverage; verify in the Documentation.

Q: Does Metals-API offer a free trial?
A: No free trial is offered. Choose a plan that fits your usage and endpoint needs; for plan details and management, see MCP.

Get your key and start fetching FE-CR in minutes

Grab an API key and test the latest FE-CR with a single curl, then wire the time-series and OHLC endpoints into your charting stack. Create your account here: Register. For full parameters and examples, see the Documentation and confirm FE-CR on the Symbols page.