Internal tools recipe
SEC API Retool Dashboard
A self-serve Retool REST API resource recipe for internal tools teams that want SEC filing watchlists, filters, and tables without maintaining an EDGAR ingest service.
REST API resource: SEC Event Intelligence
Base URL: https://sec-event-intelligence.p.rapidapi.com
Headers:
x-rapidapi-host: sec-event-intelligence.p.rapidapi.com
x-rapidapi-key: YOUR_RAPIDAPI_KEY
Query: watchlistChanges
Method: GET
Path: /v1/sec/watchlist/changes
URL parameters:
tickers = {{ tickerInput.value || "AAPL,MSFT,NVDA" }}
since = {{ sinceDate.value || "2026-07-01" }}
limit = 25
Table data:
{{ watchlistChanges.data.data.flatMap(group =>
(group.changes || []).map(change => ({
ticker: group.ticker,
form: change.filing?.form,
companyName: change.filing?.companyName,
filedAt: change.filing?.filedAt,
accessionNo: change.filing?.accessionNo,
filingUrl: change.filing?.filingUrl
}))
) }}
Workflow Setup
This recipe validates whether buyers want SEC filing data inside automation tools before we build deeper app-specific support.
- Subscribe on RapidAPI and copy the generated RapidAPI key.
- Create a Retool REST API resource with the RapidAPI base URL and required headers.
- Create a GET query for /v1/sec/watchlist/changes and bind ticker/date controls to URL parameters.
- Bind the flattened response rows to a Retool table, then add filters, buttons, or alert workflows as needed.
Endpoints Used
The integration uses live SEC Event Intelligence endpoints available through RapidAPI subscriptions.
GET /v1/sec/watchlist/changesGET /v1/sec/company/{ticker}/profileGET /v1/sec/forms/{accessionNo}/summary
Integration FAQ
Is this an official Retool template?
No. It is a REST API resource recipe that shows how to call the live RapidAPI endpoint from a Retool app.
Where should the RapidAPI key be stored?
Store it in the Retool resource authentication or header configuration rather than in visible app inputs, table data, or source-controlled app code.