Skip to content
Book a demoStart free
Connectors

Alpaca Broker API connector

Set up the Alpaca Broker API connector in Kaivo: authentication, configuration, the 7 BigQuery tables it syncs, and answers to common questions.

Alpaca Broker API connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Alpaca Broker API data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your payment and finance data instead of moving it.

Sync your Alpaca Broker accounts, activities, and assets into BigQuery with Kaivo to report on account growth, trading activity, and balances.

CategoryFinance & Payments
AuthenticationUsername and password
SetupSelf-service

Getting started with the Alpaca Broker API connector

Section titled “Getting started with the Alpaca Broker API connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Alpaca Broker API account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Connect with your Alpaca Broker API login. You provide:

Field Description
Password
Your Alpaca API Secret Key. Found in the Alpaca developer console under your account settings.

|

Configuring the Alpaca Broker API connector

Section titled “Configuring the Alpaca Broker API connector”

When you set up the connector, you provide:

Field Description
Environment
The Alpaca environment to connect to. Use Production for live data; Paper trading and Sandbox are for testing.

| | Username |

Your Alpaca API Key ID.

| | Start Date |

Any data before this date will not be fetched.

|

Tables and columns synced from Alpaca Broker API

Section titled “Tables and columns synced from Alpaca Broker API”

Kaivo syncs 7 tables from Alpaca Broker API into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

account_documents (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
date STRING
id STRING
name STRING
sub_type STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
accounts (12 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
account_number STRING
account_type STRING
created_at STRING
crypto_status STRING
currency STRING
id STRING
kyc_results__summary STRING
last_equity STRING
status STRING
trading_type STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
accounts_activities (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
description STRING
account_id STRING
activity_type STRING
date STRING
id STRING
net_amount STRING
status STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
assets (17 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
class STRING
cusip STRING
easy_to_borrow BOOL
exchange STRING
fractionable BOOL
id STRING
maintenance_margin_requirement FLOAT64
margin_requirement_long STRING
margin_requirement_short STRING
marginable BOOL
name STRING
shortable BOOL
status STRING
symbol STRING
tradable BOOL
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
calendar (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
close STRING
date STRING
open STRING
session_close STRING
session_open STRING
settlement_date STRING
uuid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
clock (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
is_open BOOL
next_close STRING
next_open STRING
timestamp STRING
uuid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
country-info (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
record STRING
uuid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Alpaca Broker API supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Alpaca Broker API?

Section titled “How long does the initial sync take for Alpaca Broker API?”

It depends on how much history is in your Alpaca Broker API account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Alpaca Broker API’s schema changes?

Section titled “What happens when Alpaca Broker API’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Alpaca Broker API, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Alpaca Broker API instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Alpaca Broker API connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Alpaca Broker API data

Section titled “Common use cases for Alpaca Broker API data”

Track accounts by created_at, status, and type to see sign-ups and active accounts over time.

Use accounts_activities with activity_type and net_amount to analyse trades, transfers, and fees per account.

Report on assets by class and exchange to see which instruments are tradable.

Join account_documents with accounts to track KYC and document status across the book.

Use Alpaca Broker API data in your AI and BI tools

Section titled “Use Alpaca Broker API data in your AI and BI tools”

Once Alpaca Broker API data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Alpaca Broker API data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Alpaca Broker API connector pricing and plan details.