Rebuild a filing's enhanced data
Start a new enhanced-data build for a US filing, even when a current one is stored, and return 202 with IN_PROGRESS; poll GET /filings/{filingId}/enhanced-data until it is DONE. A build already in progress is reported instead of starting another. A filing with no transactions returns 200 with DONE and null data. Only the organization's own filer can rebuild, as for PUT /filings/{filingId}/submission: self-managed filings must be enabled, and a partner member must be assigned to the organization or the organization assigned to no member. Returns 403 otherwise. Allows 10 requests per minute for each portfolio, or for each organization when there is no portfolio; past that it returns 429.
Authorization
Headers
Release date, as YYYY-MM-DD. Defaults to 2026-07-21.
Target organization id (Organization-Id selector).
Target connection id; resolves to its organization.
Platform entity id; resolves to a connection's organization.
Optional source to disambiguate an Entity-Id.
Path parameters
The unique identifier of the filing.
Query
Every query parameter below is optional. Combine as many as you need and append them to the endpoint as a query string. The example shows a few to get you started.
/filings/{filing_id}/enhanced-data/rebuild?jurisdiction=<jurisdiction>Two-letter code of the filing's US state, such as NY. Must match the filing.
Response
DONE, IN_PROGRESS, or FAILED.
IN_PROGRESSDONEFAILEDId of the stored build, to correlate polls and rebuilds. Null for a filing with no transactions, which has nothing to build.
The enhanced data. Null unless status is DONE, and null for a DONE filing with no transactions.
Successful Response
The request was invalid.
Authentication failed or was missing.
The credential is not permitted for this request.
The requested resource was not found.
The request conflicts with existing state.
The request failed validation.
The caller is over a rate or usage limit.