/api/v1/sec/filings/poll/triggerRequest a manual SEC filing refresh
Run the existing manual SEC filing-feed refresh and return its acknowledgement. Requires an authenticated customer identity; no administrator role or request body is required.
freeShared service-side manual-refresh cooldown; the default is 30 seconds and the deployment can configure it. Respect the wait reported in a 429 response.Since 3.155.5
Why use this
Request an immediate refresh of the latest filing feed, then use the filing-list endpoint to inspect available records. The request waits for the refresh call to return. A successful acknowledgement does not certify that every filing or downstream financial calculation has completed.
This existing customer-accessible operation refreshes the latest filing feed without a ticker, company or historical-range selector. The service applies a shared manual-refresh cooldown before starting work. Requests during that cooldown return 429 with an estimated wait in the error message. A failed refresh can also consume the cooldown window. Missing authenticated identity is rejected before refresh work starts.
Response schema
| Field | Type | Nullable | Description |
|---|---|---|---|
| status | string | no | The manual refresh call returned successfully. |
| request_id | string | yes | Request correlation identifier; null when no identifier was attached. |
| timestamp | string | no | Response creation time in UTC, ending in Z. |
| data | object | no | Refresh acknowledgement, not a filing count or downstream processing receipt. |
| data.message | string | no | Acknowledges that the existing manual refresh call returned. |
| data.timestamp | string | no | UTC acknowledgement time in ISO 8601 form, without a timezone suffix in the existing response. |
Sample response
·
- "status": "success"
- "request_id": "manual-refresh-example"
- "timestamp": "2026-09-13T14:00:00.000000Z"
- "data":
- "message": "Manual poll triggered successfully"
- "timestamp": "2026-09-13T14:00:00.000000"
Errors
| Status | Label | Description |
|---|---|---|
| 200 | OK | Request succeeded. |
| 400 | Bad Request | Invalid query, body, or path parameter. |
| 401 | Unauthorized | Missing or invalid Authorization header / api_Token. |
| 402 | Payment Required | Insufficient token balance for this call. Top up |
| 429 | Too Many Requests | Rate limit exceeded for your tier (see /pricing for tier limits). Tier limits |
| 500 | Server Error | Unexpected server-side failure. Retry with backoff; report if persistent. |
Code samples
curl -X POST "https://api.finradar.ai/api/v1/sec/filings/poll/trigger" \
-H "Authorization: Bearer YOUR_JWT_TOKEN"Generate an API key in /account/credentials to run live queries (literal YOUR_API_KEY placeholder shown until then).