Version analytics

The restatement timeline tells you that a period was revised and how severely. These routes tell you what the revision did to a number you care about.

All of them identify a period the same way: statement_type, fiscal_year and fiscal_period, with cik or ticker naming the company.

Which route answers which question

Metric drift

curl -X GET "https://api.arche.fi/v1/analysis/metric-drift?ticker=AAPL&statement_type=INCOME_STATEMENT&fiscal_year=2024&fiscal_period=FY&metric=REVENUE" \
  -H "X-Api-Key: $ARCHE_API_KEY" \
  -H "Accept: application/json"

A period no filer revised answers 200 with nothing moved, which is an answer rather than a gap. /v1/edgar/restatement-alerts lists the periods that were revised, so start there when you want a period with drift in it.

metric must be a canonical statement metric. This route reads filed facts only, so a market-dependent derived metric is refused rather than estimated. See the metric catalog for which names are which.

Version delta

The same shape, comparing the original against a specific later version instead of against the latest:

curl -X GET "https://api.arche.fi/v1/analysis/version-delta?ticker=AAPL&statement_type=BALANCE_SHEET&fiscal_year=2024&fiscal_period=FY&metric=TOTAL_ASSETS" \
  -H "X-Api-Key: $ARCHE_API_KEY" \
  -H "Accept: application/json"

Market-dependent metrics are refused here too, for the same reason.

Delta between two named versions

When the question is "everything that changed", not one metric, name the two versions and read the whole diff:

curl -X GET "https://api.arche.fi/v1/edgar/statements/restatements/delta?ticker=AAPL&statement_type=BALANCE_SHEET&fiscal_year=2024&fiscal_period=FY&from_accession={from_accession}&to_accession={to_accession}" \
  -H "X-Api-Key: $ARCHE_API_KEY" \
  -H "Accept: application/json"

Name the versions with exactly one selector pair, either from_accession and to_accession or from_statement_version_id and to_statement_version_id.

Model impact

What the revision did to derived figures across the version lineage, rather than to a filed fact:

curl -X GET "https://api.arche.fi/v1/analysis/model-impact?ticker=AAPL&statement_type=INCOME_STATEMENT&fiscal_year=2024&fiscal_period=FY" \
  -H "X-Api-Key: $ARCHE_API_KEY" \
  -H "Accept: application/json"

Unlike the two routes above, this one can depend on market inputs, because persisted metrics such as MARKET_CAP and ENTERPRISE_VALUE may be present in the lineage. When they are, the route requires you to acknowledge that with allow_market_inputs=true, so a figure that depends on a price is never returned to a caller who believed they were reading filings alone.