alpaca-broker-funding-transfers
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta funding wallet (international/instant), transfer status lifecycles, and fees. Use when building deposit/withdrawal flows or connecting external bank accounts on Alpaca in any language. For moving cash/shares BETWEEN accounts inside your own omnibus, use journals instead.
npx skills add alpacahq/alpaca-skills --skill funding-transfers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Alpaca Broker API — Funding & Transfers Getting cash into and out of end-user accounts. There are **three rails**, and the model splits cleanly into *bank links* (persistent) and *transfers* (the actual money movement). > Read `alpaca-broker-integration` first. Broker API + HTTP Basic auth. For moving cash *between* accounts in your omnibus (vs. to/from the outside world), see `alpaca-broker-journals` — that's a different mechanism. ## Reference - Guide: `https://docs.alpaca.markets/docs/funding-accounts` - API ref: `https://docs.alpaca.markets/reference/createtransferforaccount` - Live schema: `alpaca-docs` MCP → `get-endpoint` title `"Broker API"` path `/v1/accounts/{account_id}/transfers` ## 1. The funding model ``` External bank ──(relationship: a persistent link)──┐ ├──> Transfer (the money movement) ──> Account cash ACH relationship (rail A: ACH, US domestic) │ Bank relationship (rail B: wire, domestic + intl) │ Funding wallet (rail C: v1beta, multi-currency) ┘ ``` - A **relationship** links an external bank. It moves no money and has its own status; for wires it must be `APPROVED` before a transfer can progress. - A **transfer** references a relationship by ID and moves th
- Reference
- 1. The funding model
- 2. Endpoints
- 3. Create-transfer request (POST /v1/accounts/{id}/transfers)
- 4. Wire recipient bank (POST /v1/accounts/{id}/recipientbanks)
- 5. Transfer status state machines
- 6. Events vs polling — the key reliability lesson
- 7. Documented gotchas
- 8. The omnibus / sweep-account pattern (architecture lesson)
What does the alpaca-broker-funding-transfers skill do?
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta funding wallet (international/instant), transfer status lifecycles, and fees. Use when building deposit/withdrawal flows or connecting external bank accounts on Alpaca in any language. For moving cash/shares BETWEEN accounts inside your own omnibus, use journals instead.
How do I install it?
Run `npx skills add alpacahq/alpaca-skills --skill funding-transfers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alpacahq/alpaca-skills, a repository with 106 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.