REST API | IPOGrid

Pull the joins you actually need

Most research starts from a small chain: companies -> filings -> terms/consensus -> outcomes/news. Use OpenAPI when you need the full endpoint schema.

Find a known ticker and include useful joins

curl -H "Authorization: Bearer $IPOGRID_API_KEY" \
  "https://ipogrid.com/api/v1/companies?scope=all&q=spcx&include=latest_terms,classification,consensus"

Fetch company detail by ticker

curl -H "Authorization: Bearer $IPOGRID_API_KEY" \
  "https://ipogrid.com/api/v1/companies/spcx?include=filings,news,latest_terms,classification,consensus,financial_snapshot"

Pull recent outcomes

curl -H "Authorization: Bearer $IPOGRID_API_KEY" \
  "https://ipogrid.com/api/v1/outcomes?trading_start_date_from=2026-06-01&limit=100"

Public article feed

curl "https://ipogrid.com/api/v1/articles?limit=30"

API rules of thumb

Use CIK for durable joins. Use ticker for lookup, then keep the resolved CIK. Use cursor pagination for list endpoints. Use `include` only for data you need; rich includes cost more work than identity rows.

Use research workflows when you want backtest-oriented examples.