# Company resolution and statement retrieval

This is the basic operational workflow for moving from a ticker to actual Arche statement data.

## Resolve the company

```http
GET /v1/edgar/companies:resolve?ticker=AAPL
```

Use the resolved company record to obtain the canonical `cik`.

## Inspect filings

Once you have a `cik`, you can inspect filing history.

```http
GET /v1/edgar/companies/{cik}/filings
```

If you need a single filing:

```http
GET /v1/edgar/companies/{cik}/filings/{accession_id}
```

## Retrieve statements

List company statements directly:

```http
GET /v1/edgar/companies/{cik}/statements?statement_type=INCOME_STATEMENT&page=1&page_size=10
```

Or inspect statements within a specific filing:

```http
GET /v1/edgar/companies/{cik}/filings/{accession_id}/statements
```

This is the route split to keep in mind:

- filing routes answer document-history questions
- statement routes answer normalized-financial-data questions

## Move into point-in-time analysis

Once you know the issuer and the statement family you care about, switch to point-in-time retrieval when the historical boundary matters.

```http
GET /v1/edgar/as-of/{date}/financials/{cik}
```

## Next steps

- [Restatement drift](https://docs.arche.fi/guides/restatement-drift): Show how restatements change historical results when data is not queried point-in-time.
- [Point-in-time research](https://docs.arche.fi/guides/point-in-time-research): Build research workflows that preserve historical knowability and reproducibility.
- [Rebuild a historical view](https://docs.arche.fi/guides/rebuild-historical-view): Reconstruct what a company statement looked like on a specific date.