I deleted line items through the API — can I recover them?

Yes — but through the Allocadia UI Recycle Bin, not the API. The public API has no restore endpoint. Disable the connection first.

What this answers:

• Whether deleted line items can be restored, and through which channel
• The critical first step before attempting any restore
• What to do if items aren't in the Recycle Bin

Short answer

Yes, deleted line items can usually be recovered — but through the Allocadia UI Recycle Bin, not through the API. The public Allocadia REST API supports GET, POST, PUT, and DELETE on line items but does not expose a restore, undelete, or recycle-bin endpoint. So whatever integration performed the deletes cannot reverse them through the same channel.

Don't try to recreate the line items via POST. POSTing creates new line items with new IDs. That breaks PRs, BI Export joins, reporting references, and anything else keyed on the original line item IDs. The result is look-alikes, not the originals back.

Step 1 — Disable the connection that performed the deletes

Before anything else, pause the script, integration, or token that ran the bad delete operation. If you don't, whatever logic triggered the deletes will fire again on the next sync and undo your restore work.

Step 2 — Try the Allocadia UI Recycle Bin

Each Sub-Category has a Recycle Bin where deleted items land, including those deleted via the API.

1. Open one of the affected Sub-Categories.
2. Locate the Recycle Bin view.
3. Find the deleted line items in the list.
4. Restore them one at a time (the Recycle Bin does not have a bulk-restore action). Restoring one as a test first lets you confirm everything comes back clean — PR links, attribute values, percentages — before working through the rest.

![SCREENSHOT NEEDED: Recycle Bin in a Sub-Category showing deleted items]

Step 3 — If the Recycle Bin doesn't have them, or restore fails

If items aren't in the Recycle Bin or the Restore action returns an error, contact Support right away. Bring the following information so we can route the request to the right team:

• The approximate time window of the bad deletion run (UTC if possible)
• The names of the Sub-Categories affected
• A sample of the deleted line item IDs (from your records, or from the audit view)
• Confirmation that the integration that caused the deletes is disabled

Restoring from the soft-delete state directly isn't a guaranteed self-serve path — the sooner you raise it, the better.

Related articles

• Recycle Bin restore in Allocadia returns an error
• The Allocadia REST API — overview of endpoints
• Deleting records via the Allocadia API — what to know first
• Recovering deleted items from the Allocadia Recycle Bin