Skip to main content
GET
Get Import Details
Retrieve the full details of a policy import, including all extracted rules and their properties. Use this endpoint to poll for results after submitting an import, and to review rules before activation.
Extraction runs in the background. Small documents are usually pending_review within seconds; large documents (hundreds of pages) are extracted in chunks and can stay in processing for several minutes. Poll until the status is no longer processing.

Path Parameters

string
required
The import ID returned from the import endpoint

Response

string
Unique import identifier
string
Account the import belongs to
string
Import status: processing, pending_review, no_rules_found, failed, activated, or partially_activated
string
Where the document came from: a connector’s provider slug (notion, linear, atlassian, google_drive) when a connected workspace produced it, uploaded when it was staged through this API as a file, or built when it was authored in your own UI. Treat this as an open set — a new connector adds a new slug.
string
How the content was submitted: file or text
string
How the stored document is read during extraction: raw for uploaded bytes, text for plain text
string
Original filename, when the import was submitted with one
integer
Number of extracted rules (present once extraction completes)
string
ISO 8601 timestamp of the import
string
ISO 8601 timestamp of the most recent activation, when any rules have been activated
array
Customer-prefixed rule IDs activated from this import, sorted. Present once at least one rule has been activated.
string
Error details when status is failed
array
Full list of extracted rules with details. Every rule carries the whole field set; fields that do not apply to the rule’s type are returned as null.

Connector provenance

Imports produced by a connected workspace also carry the audit trail of where the document came from. These fields are absent on documents uploaded through this API.
string
Connector that produced the document
string
The connection the document was fetched through
string
The provider’s own identifier for the source document
string
The document’s URL at the provider, recorded verbatim
string
The document’s title at the provider, when it has one
string
Who the provider says last edited the document
string
When the provider says it last changed, in the provider’s own format
string
The MCP tool whose result carried the document
string
Digest of the imported content as sha256:<hex>. Re-importing content with this digest is a no-op.
integer
Size of the document the connector fetched, as the connector measured it
string
Media type the provider reported for the document, e.g. text/markdown
string
When the connector fetched the document, ISO 8601 UTC

Errors