Direct access request recorded

SEC API direct access

The direct access request path has recorded your request. API checkout and key provisioning can continue through the self-serve RapidAPI route immediately while a hosted MCP or direct-key path is reviewed. Requested workflow: Form 4 insider filings.

Run Form 4 in RapidAPI Playground Subscribe on RapidAPI Form 4 quickstart Download Python runner Download JavaScript client 5-minute quickstart Import Postman Download Postman collection Estimate volume Review MCP access Run MCP browser demo MCP first tool-call JSON Access JSON Support and review

Continue without waiting

REST buyers can subscribe through RapidAPI immediately, copy the generated key, and verify the requested endpoint with the matching playground, Python runner, quickstart, or Postman collection.

Requested workflowUse the Form 4 quickstart when the direct-access request came from insider transaction or Form 4 filing workflows.
REST checkoutRapidAPI manages subscription, billing, quotas, and generated snippets
Run nowOpen Form 4 insider filings in RapidAPI Playground and confirm an HTTP 200 response before copying code
First callRun Form 4 quickstart for GET /v1/sec/insider-trades?ticker=MSFT&limit=25
Python runnerDownload the one-request runner at /downloads/sec-event-intelligence-first-call.py for a terminal, worker, or serverless environment
Node.js pathDownload the JavaScript client or copy the native fetch example from the first-call page
Postman importUse /postman.json or the public Postman workspace for endpoint review
Plan fitEstimate monthly request volume before moving scheduled jobs to a paid plan
MCP production dataUse hosted MCP access only when a client needs tool calls through https://api.data-apis.com/mcp

First authenticated request checklist

The fastest production path is one successful REST request from the subscribed RapidAPI app. Run the requested workflow in Playground first, then move the same request into a backend job or imported client.

1. Subscribe RESTCreate the RapidAPI app key for protected SEC endpoints
2. Run first requestRun Form 4 insider filings in RapidAPI Playground and confirm HTTP 200 JSON with data and meta
3. Confirm trafficConfirm RapidAPI traffic from the subscribed app before copying snippets into a worker or backend job
4. Import assetsDownload Postman collection or download the Python runner
5. Schedule safelyStore the key in a server-side environment variable and review expected volume in the pricing calculator
6. MCP only if neededRequest hosted MCP access only when production tools/call must run through https://api.data-apis.com/mcp

Self-serve handoff

A hosted MCP access request should not block REST evaluation. Use the machine-readable handoff and import files to keep the API review moving while production MCP access is reviewed.

Access JSONOpen the access handoff for REST checkout, hosted MCP, pricing, OpenAPI, and no-key evaluation links
Postman collectionDownload collection JSON and pair it with the public environment file
MCP first actionRead first public tool-call JSON for sec_demo_latest_filings and sec_subscription_info
REST defaultSubscribe on RapidAPI when the client can call HTTP endpoints directly

MCP no-key path

Hosted MCP buyers can verify the remote server and public setup tools before a production key is issued. Use the browser runner for the fastest check, or download the JSON payloads for an MCP client or terminal workflow.

Browser runnerRun the MCP browser demo for public tools/call checks without an API key
Demo toolDownload sec_demo_latest_filings JSON to confirm response shape
Access handoffDownload sec_subscription_info JSON for RapidAPI REST checkout and hosted MCP access links
Production routeReview MCP access after public setup calls succeed