Start Import
Custom Policies
Start Import
Start rule extraction after uploading a policy file via presigned URL
POST
Start Import
Step 2 of the large-file custom policy import flow (after the S3 upload). Call this after uploading your file to the
presigned
upload_url from Get Import Presigned URL.
It verifies the uploaded object and enforces the size cap, then — once malware scanning has
completed successfully — starts asynchronous rule extraction and returns status: "processing".
If the scan is still running, it returns status: "scan_pending" immediately instead; retry the
call until extraction starts (see the note below).
Poll Get Import Details until the status
transitions to pending_review, no_rules_found, or failed — identical to the inline
Import Policy flow.
Request Body
The
import_id returned by Get Import Presigned URL.Optional filename to record on the import (overrides the value from the presigned step).
Response
Unique identifier for the import. Use it to poll for status or activate rules.
processing once extraction has started, or scan_pending if the malware scan is still
running (retry shortly).Human-readable message with next steps.
Error Responses
| Status | Description |
|---|---|
| 400 | Missing/invalid import_id, or the uploaded file is empty |
| 403 | Invalid API key, or the import belongs to another customer |
| 404 | No uploaded file found for this import_id (upload step skipped or failed) |
| 409 | Import already started or completed |
| 413 | Uploaded file exceeds the maximum allowed size (1 GB) |
| 422 | File failed malware/content scanning |
If you receive a
202 with status: "scan_pending", the malware scan is still running
(usually a few seconds). Retry this request shortly — rule extraction does not start until the
scan completes successfully.
