Skip to main content

Delete a connected Library document (beta)

Delete from Apostra is a beta capability for enabled seller accounts. It uses the V3 save_material tool and is available to a directly signed-in seller administrator. Apostra staff can also perform this workflow when a seller asks us to remove a document, using a direct, elevated staff session for that seller account. Library marks a pending deletion that Apostra staff scheduled so the seller can see who scheduled it. API keys, service credentials, delegated support, and agent credentials cannot preview, schedule, or Undo a deletion. The beta accepts exactly one document per preview, delete, or Undo call. In Library, seller administrators can select imported files. In Integrations, they can open a connected folder to list its imported files in Library. Before confirming a deletion, Library shows the count and names of affected saved proposals. The same administrator can Undo during the 30-day window or choose Include again after an exclusion is active. Deletion is destructive. Scheduling it archives the document immediately, excludes its connected-source item so sync cannot import it again, and removes the document from new proposal composition. Preview the affected saved proposals before confirming. At the end of the 30-day Undo window, Apostra purges the document and redacts saved proposal text, proposal artifacts, and compose inputs that used or cited it. Copies already sent to buyers cannot be recalled.

V3 save_material actions

Use the action calls below only for this beta workflow. Each delete and Undo names one materialId. Preview first, inspect the impact, and pass its confirmation to the delete call:

Review document-applied insights

The deletion preview also returns appliedInsights: one row for every insight the document applied to a Playbook, Business Rules, Wholesale product, Signal, or Seller listing. Each row includes its applicationId, source revision, destination type and label, proposed disposition, and pendingRemoval state. Use insightDispositions with delete_permanently to change an individual row. Each entry is { applicationId, disposition }, where disposition is remove or keep; you can send at most 100 entries. Omitted rows use the preview default. The confirmation is tied to the exact set of applied insights, so preview again if it changes. Scheduling deletion marks every listed insight as pending for the 30-day Undo window. It does not change a destination record while that window is open. undo_permanent_delete restores the document and clears those pending markers. This delivery records the selected outcome; the later terminal deletion step will apply it to destination records. Undo uses the same document identity:
Include again is a separate, explicit choice; it never happens as part of a sync, reconnect, cleanup, or Undo:
Undo restores the document but does not lift its connected-source exclusion. Sync never lifts an exclusion. Use the explicit Include again seller action when you want a fresh copy of the connected item imported, including after the purge has completed. For importing and maintaining Library material, see Bring data in.

Beta release check

Brian O’Kelley owns the beta release check. Immediately after exposing the beta to a seller, and before that seller’s 30-day window ends, he runs one real preview, schedule, and Undo on a disposable connected Library document. The check passes only when the receipt records the same document and seller, the document archives immediately, Undo restores it, and its source remains excluded. If any step fails or the receipt disagrees, pause new beta exposure and disable the beta before a scheduled purge can run. If Undo fails, do not leave the disposable document scheduled for deletion: remediate the failure and retry Undo until it succeeds. Investigate before enabling another seller.