Support

Ask a question or report a problem in the support forum. It is open to everyone and does not need an Alpaca account — a GitHub account is enough.

⚠️ Never post an API key or secret. Not in a screenshot, not in a log. If one has been shared anywhere, revoke it in your Alpaca dashboard and create a new pair — it takes a few seconds and is the only safe response.

“Rejected credentials” when connecting

Alpaca answers a bad key with a bare unauthorized, which looks the same whatever the cause. In practice it is almost always one of these:

Paper keys on a live account, or the reverse

They are different key pairs and are not interchangeable. A paper key ID begins with PK, a live one with AK — Logbook checks this before it sends anything, so if it let the request through, the pairing was right.

The same value in both fields

Easy to do when copying twice from the same page. The key ID is 26 characters and the secret is 44 — if they look similar in length, something is wrong.

A truncated paste

A missing first or last character fails identically to a wrong key.

Keys that were regenerated

Creating a new pair in the Alpaca dashboard invalidates the old one immediately, including in any bot still using it.

The realised figure differs from Alpaca’s dashboard

It should, and Logbook’s is the one that answers “what did I make”.

Alpaca’s activities list shows cash proceeds per fill — the money that moved when each order executed. It is not profit, because it never pairs an entry with its exit. Logbook does that pairing on your device, first in first out per symbol, and reports the result of each completed round trip.

Positions still open are excluded, because nothing is realised until a trade closes.

The total doesn’t match my account balance

Check whether you are reading the gross figure or the net one. Alpaca charges no commission on equities, but it passes on SEC, FINRA and CAT fees. They are billed per day rather than per trade, so History shows them as their own rows and nets them into a separate Net line. That net figure is the one that reconciles with your balance.

If a period filter is on, the total covers only that period.

A symbol shows “no data”

Prices come from Alpaca under your own data plan. On the free plan that is the IEX feed only — a fraction of consolidated volume — so thinly traded symbols can have no recent print, and the volume shown is IEX’s own rather than the full tape. Logbook labels it that way rather than presenting it as the market’s volume.

Market hours look wrong

They are shown in your device’s timezone, not New York’s. If you are in Central Europe, the US open is late afternoon.

“Connection limit exceeded”

Alpaca permits one market-data stream per account, and something else — usually your own trading bot — already holds it. Logbook polls over REST and does not open a stream, so this points at another client rather than at Logbook.

Restoring your purchase

The unlock is a one-off purchase tied to the store account you bought it from. On a new device, open Logbook and choose Restore purchase. If it reports nothing found, check you are signed in with the account that paid — your Apple Account on iPhone and iPad, your Google Account on Android.

The two stores do not share purchases. Buying on iPhone covers iPad, because Apple treats them as one account; it does not cover an Android phone, and an Android purchase does not cover an iPhone. That is how both stores work rather than a choice Logbook makes.

Can Logbook place trades?

No. It has no ability to place, change or cancel an order — the capability is absent from the app, not switched off. Logbook shows you what an account did; something else does the trading.

Something else

Open a thread in the support forum. Saying which device and OS version, whether the account is paper or live, and what you expected to see is usually enough to get to the answer quickly.