7.7Using the Recycle Bin from the REST API

The Recycle Bin is available to integrations on the machine surface under /api/ad/deleted-objects. All routes need the recycle-bin licence feature and act on the directory selected by the request's connection. The Recycle Bin is not offered as an AI-agent tool or as an n8n operation.

A restore request body has two optional fields, targetParentDn and newName. An empty body restores the object in place under its original name:

{
  "targetParentDn": "OU=Staff,DC=example,DC=com",
  "newName": "Jane Smith (restored)"
}

The response states where the object landed and whether it came back stripped:

{
  "objectGuid": "3f2c…",
  "distinguishedName": "CN=Jane Smith (restored),OU=Staff,DC=example,DC=com",
  "name": "Jane Smith (restored)",
  "objectClassName": "user",
  "restoredToAlternateParent": true,
  "attributesNotPreserved": false
}

A reapply request may name a subset of the attributes from the plan in attributes; an empty list writes everything the plan marked writable. The list can only narrow the plan, never add to it. The reapply route answers 404 when no usable image is held.

When the caller is an API key subject to approval, the restore and reapply routes can answer 202 Accepted with an operation handle instead of the result. See Chapter 15, REST API for integrators.

Troubleshooting