Snapshot extend
BetaAdd one module to a completed snapshot without starting a new research job.
Beta
Overview
After a job completes, the result is stored as a snapshot. POST /v2/snapshots/{snapshot_id}/extend adds exactly one module to that snapshot and returns the updated body.
Extend is synchronous. It does not create a new job_id and you do not poll. Use the snapshot_id from a completed job.
Use extend when the first run used plan: "core" (or another subset) and you later need OSHA, Form 5500, adverse news, or another priced module.
Modules
These module ids are accepted. Sending any other id — including trade_licenses — returns 400.
| Module | Credits |
|---|---|
| Adverse newsadverse_news | 3 |
| Business risk flagsbusiness_risk_flags | 4 |
| Digital riskdigital_risk | 4 |
| Restricted listsofac_restricted_lists | 0 (no charge) |
| OSHAosha | 2 |
| Liquor licensesliquor_licenses | 0 (no charge) |
| Property financialsproperty_financials | 5 |
| Form 5500form_5500 | 2 |
| FMCSA / SAFERfmcsa_safer | 2 |
| IRS Form 990irs_990 | 2 |
| Producer reportproducer_report | 2 |
Add a module
Send exactly one module. Optional refresh_summary regenerates the executive summary after the module is added.
POST /v2/snapshots/{snapshot_id}/extend
Already present
If that module is already on the snapshot, the API returns 409. Use idempotency_key so a retried extend reuses the same amendment instead of charging again.
Billing
Extend charges only that module at the credit weight in the table above. A degraded or failed extend refunds those credits. See Credits.