Data Downloads

Download and work with Radar data files.

Available Files

File	Description	Format	Size
events.parquet	Full event data	Parquet	~150 MB
events_index.parquet	Lightweight index	Parquet	~15 MB
events_sample.csv	Free sample	CSV	~1 MB

Download Methods

1. Web Dashboard

The easiest way to download data:

1. Go to radar.matchstick.trading
2. Sign in with your account
3. Navigate to Events > Raw Data Access
4. Click Download Parquet or Download Index

2. REST API

Using curl with authentication:

# Download events.parquet
curl -H "Authorization: Bearer YOUR_API_KEY" \
  -o events.parquet \
  "https://radar.matchstick.trading/api/downloads/events.parquet"

# Download index
curl -H "Authorization: Bearer YOUR_API_KEY" \
  -o events_index.parquet \
  "https://radar.matchstick.trading/api/downloads/events_index.parquet"

Free Sample

A free sample CSV is available without authentication:

curl -o events_sample.csv \
  "https://radar.matchstick.trading/api/downloads/events_sample.csv"

Sample contents (~1000 recent events):

id,event_type,issuer,cik,filed_at,transaction_code,shares,price_per_share,total_value
sec:form4:abc123,FORM_4,APPLE INC,0000320193,2025-01-15T14:30:00Z,P,1000,185.50,185500
...

Data Freshness

Data is updated on a schedule:

File	Update Frequency
events.parquet	Every 6 hours
events_index.parquet	Every 6 hours
events_sample.csv	Daily

Check the last update time via the API:

curl "https://radar.matchstick.trading/api/system-status" | jq '.last_sync'

Incremental Updates

For incremental updates, use the REST API with date parameters:

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://radar.matchstick.trading/api/events?start=2025-01-08&end=2025-01-15"

Verification

Verify file integrity using checksums:

# Get checksum from API
curl "https://radar.matchstick.trading/api/system-status" | jq '.files.events_parquet.checksum'

# Verify local file
sha256sum events.parquet

Storage Recommendations

For production use:

1. Store locally - Keep a local copy for fast access
2. Automate updates - Use a script to poll the API for new data
3. Version files - Keep historical snapshots for reproducibility
4. Verify checksums - Always verify after download