// alpaca import

Your Alpaca Trading Journal

Journal your Alpaca trades without re-typing them. Download your order history from the Alpaca dashboard, drop the CSV in, and TickerScribe recognizes it by its columns — every filled order at the price it executed, the ones that never filled named rather than quietly dropped.

One file in · stocks & ETFs · 100% free

// how-to-export

From your Alpaca orders to your journal

Four steps, about a minute — and the last two are the same on every broker.

  1. 01

    Open your order history in Alpaca

    In the Alpaca dashboard, go to your orders and set the date range you want — the whole history, or just the window you haven't journaled yet.

  2. 02

    Download it as a CSV

    Take the export as-is. Every column stays where it is, nothing needs deleting, and a file that has been through a spreadsheet on the way still imports.

  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: what imports, what was set aside and why, and which rows you already have. Then trades post to the ledger.

// auto-detected

Orders in, trades out.

The orders export is one row per order, with the quantity that filled and the price it filled at. TickerScribe books what executed, leaves out what didn't, and tells you which is which before anything is saved.

alpaca_orders.csvAlpaca · auto-detected
Asset,Side,Position Intent,Filled Qty,Avg. Fill Price,Status,Filled Atcolumns mapped
MRDN,buy,buy_to_open,50,84.30,filled,"Jun 2, 2026, 10:14:22 AM"stock · opened
SLST,sell,sell_to_close,30,19.62,filled,"Jun 4, 2026, 1:47:05 PM"stock · closed
AXDN,buy,buy_to_open,25,127.55,partially_filled,"Jun 8, 2026, 9:31:11 AM"stock · the part that filled
TRQV,buy,buy_to_open,0,-,canceled,-never filled · named, not dropped

Stocks & ETFs·Only some of the export's eighteen columns are shown here. You don't need to touch the rest.

What comes acrossFrom one file

Every filled order, at the price it executed

The export states each order's average fill price with up to six decimals, and that's the figure TickerScribe books — not a rounded total divided back out. An order that filled part way imports for the part that filled, at that part's own price.

Orders that never filled are named, not dropped

An order where nothing filled at all moved no shares, so there's no trade in it — but it's counted and named on the preview instead of vanishing, and you can see exactly how many were left out. The test is the quantity that filled, not the status: an order that was cancelled after filling part way still imports, for the part that filled.

The open or close the export states

Where the export states a position intent — bought to open, sold to close, and the two short-side spellings — TickerScribe reads it instead of inferring a direction from the side alone, so a short stays a short and a cover stays a cover. Orders that state none fall back to their buy-or-sell side.

A file that has been through a spreadsheet

Plenty of these exports arrive after a trip through Sheets or Excel, which adds a stray index column and rewrites every timestamp into words. Both are read as they are — the columns are matched by name, and the reformatted dates are understood.

The clock you traded on

This export states no time zone of its own, so TickerScribe doesn't invent one: it reads the times as the clock you were looking at, starts from your own zone, and shows you which one it's using on the preview step — where you can change it before anything is saved.

Options and crypto, set aside by name

Both trade through the same grid, and neither imports from this export: it states no contract multiplier, so reading an option's amounts off it would risk booking the wrong ones. They're counted and named on the preview rather than guessed at.

Safe re-imports

Repeated rows are flagged on the preview step before anything posts, and each order's own id is checked again as trades are written — so an order the export has since restated is still recognized rather than booked twice. Overlapping date ranges are safe to import.

One minute, one CSV

Your whole Alpaca history, in one place

No credit card required. Download your orders, drop the CSV in — every filled order comes across at the price it executed.

Frequently Asked Questions

Is TickerScribe really free?
Yes — completely free, no credit card, no trade caps. Import your full Alpaca order 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?
Export your orders from the Alpaca dashboard. Open your order history, set the date range you want, and download it as a CSV — that file is recognized the moment you drop it in, and every column is mapped for you. TickerScribe reads the CSV you provide: it never connects to your Alpaca account and never asks for your API keys.
Which Alpaca export should I use?
The dashboard orders download, for almost everyone — it's a button, it covers every order, and it's recognized automatically. The other route is Alpaca's account activities endpoint (the FILL activity type), which is worth pulling if you want per-fill detail: an order that filled in pieces arrives as one row per piece at each piece's own price, instead of one row at the order's average. Both are auto-detected; both import stocks and ETFs.
What happens to orders that never filled?
They're set aside and counted, never imported and never silently dropped — an order that filled nothing moved no shares, so there's no trade in it. The preview names the group so you can see exactly how many were left out. An order that filled part way is different: that one imports, for the part that filled.
Does the export show my fees?
No, and TickerScribe says so rather than pretending. Alpaca charges no commission on stocks, but it does pass the regulatory charges on sells through — and the orders export has no fee column at all, so trades import with zero fees and the preview tells you that up front. You can add a trade's fee from its Edit dialog if you track them.
Do my Alpaca options import?
Not yet. Both exports are your equity and ETF orders. Option contracts in the orders download are set aside and named in the preview — the export doesn't state a contract multiplier, so reading amounts off it would risk booking the wrong ones, and inventing that is worse than skipping it. Crypto and currency pairs are set aside the same way. Add options by hand for now, or import them from another broker that's supported.
Which clock do my trades get?
The one you saw. The dashboard renders order times in your browser's own time zone, so TickerScribe treats that as the clock you traded on and shows the zone on the preview step, where you can change it before anything is saved. The API route stamps each fill in UTC instead, and that's read as a precise moment and rendered into your own zone rather than stored as a UTC wall clock.
Can I import a long history in pieces?
Yes, and overlapping ranges are safe on both routes. Re-download a window you already imported and the repeated rows are flagged on the preview step before anything posts. The dashboard export also carries each order's own id, which is checked again as trades are written — so even an order the export has since restated is recognized and skipped rather than booked twice. The API route reuses an order's id across its fills, so those rely on the content check alone.