// alpaca import

Your Alpaca Trading Journal

Journal your Alpaca trades without re-typing them. It's a CSV import, like every other broker — Alpaca just has no download button, so you save your fills to a file yourself, then drop it in. TickerScribe recognizes it by its columns and brings every fill and partial fill across at the exact price it executed.

One file in · stocks & ETFs · 100% free

// how-to-export

From your Alpaca fills to your journal

Four steps, about two minutes.

  1. 01

    Get your fill activity

    Alpaca has no dashboard download button — it's developer-first. Pull your activity from the account activities endpoint, or the SDK's get_activities, to fetch your executions.

  2. 02

    Save the fills to a CSV

    Keep the FILL activity type — those are your real executions — and save them to a CSV with the columns Date, Symbol, Side, Qty, Price, Order ID, Type, and Cum Qty.

  3. 03

    Drop the file into the Import Wizard

    Settings → Import Data, drag the file in. It's identified as Alpaca automatically from its columns — no mapping, no cleanup.

  4. 04

    Preview & commit

    See every trade before anything is saved. Each fill and partial fill lands as its own execution at its own price, duplicates are flagged, then trades post to the ledger.

// auto-detected

Fills in, trades out.

An Alpaca activity CSV has one row per fill — the same order can appear several times as it filled in pieces. TickerScribe reads each row as its own execution at its own price, so your average cost and P&L reconstruct the order exactly.

alpaca_activities.csvAlpaca · auto-detected
Date,Symbol,Side,Qty,Price,Order ID,Type,Cum Qtycolumns mapped
2026-05-29 11:04:02.777000+00:00,MRDN,buy,50,84.30,…,fill,50stock · buy
2026-06-02 15:18:44.019000+00:00,SLST,sell,30,19.62,…,fill,30stock · sell
2026-06-04 09:31:10.500000+00:00,AXDN,buy,10,127.40,…,partial_fill,10stock · fill 1 of 2
2026-06-04 09:31:11.200000+00:00,AXDN,buy,15,127.55,…,partial_fill,25stock · fill 2 of 2

Stocks & ETFs·The last two rows are one order that filled in two pieces — booked at each piece's own price.

What comes acrossFrom one file

Every fill, at its own price

Alpaca reports each fill and partial fill of an order as its own row, at the price that piece executed at. TickerScribe imports each as its own execution — so an order that filled in pieces becomes several trades at their individual prices, and your average cost comes out exactly right.

Buys and sells, kept straight

Alpaca writes the side in lowercase — buy and sell — which TickerScribe maps to real buys and sells rather than guessing from a sign. Quantities are the incremental fill size, so nothing is double-counted.

Microsecond UTC timestamps, read directly

Each fill is stamped in ISO-8601 UTC down to the microsecond. TickerScribe reads it as-is and keeps the moment you traded — no reformatting, no broken dates.

Recognized by its columns, not a filename

There's no broker name inside the file — so TickerScribe recognizes it by its column fingerprint. Drop it in and it maps itself, however you produced it: the SDK, a script, or a notebook.

Safe re-imports

Alpaca reuses an order's ID across its fills, so TickerScribe dedupes on a content fingerprint instead. Re-running a file, or pulling overlapping date ranges, flags duplicates on the preview step and skips them.

Two minutes, one CSV

Your whole Alpaca history, in one place

No credit card required. Pull your fills, drop the CSV in — every execution comes across at the exact price it filled.

Frequently Asked Questions

Is TickerScribe really free?
Yes — completely free, no credit card, no trade caps. Import your full Alpaca fill history, journal your stock and ETF trades, and keep ledger-accurate P&L without paying anything.
How do I get a CSV out of Alpaca?
Alpaca doesn't have a download button in a dashboard the way most brokers do — it's developer-first. Pull your fill activity from the account activities endpoint (the FILL activity type) and save it as a CSV. Then you upload that file, exactly like any other broker import: TickerScribe reads the CSV you provide — it never connects to your Alpaca account and never asks for your API keys. As long as the file carries the columns Date, Symbol, Side, Qty, Price, Order ID, Type, and Cum Qty, it's recognized on upload and every column is mapped for you.
Why does one order show up as several rows?
Because Alpaca reports every fill and partial fill of an order as its own row, each at the price that piece actually executed at. TickerScribe imports each row as its own execution — so an order that filled in three pieces becomes three trades at their individual prices. This is complete and correct, just more granular than one row per order; your average cost and P&L come out exactly right.
Do my Alpaca options import?
Not yet. This export is your equity and ETF fills. Alpaca's other activity types — options, dividends, and fees — arrive with different columns and aren't matched here. Add those by hand for now, or import them from another broker that's supported.
The timestamps are in UTC with a long decimal — is that a problem?
No. Alpaca stamps each fill in ISO-8601 UTC down to the microsecond, like "2026-05-29 11:04:02.777000+00:00". TickerScribe reads it directly and keeps the moment you traded — no manual reformatting, no broken dates.
Can I import a long history in pieces?
Yes. Pull activity in date-range chunks and import them one after another. Alpaca reuses an order's ID across its fills, so TickerScribe dedupes on a content fingerprint instead — overlapping ranges are safe, and duplicates are flagged on the preview step and skipped.