Delete webclip for a tenant
⚠️ Apple devices only.
Deletes a specific webclip from the tenant library by its Esper UUID, returning the deleted webclip record. The deletion is permanent. A 409 response indicates the webclip cannot be deleted because it is currently referenced by an active blueprint or configuration.
About Delete Webclip
Deleting a webclip removes it from the tenant library and makes it unavailable for new deployments. The 200 response returns the complete Webclip record for the deleted entry — retain it for audit purposes. The 409 Conflict response is significant: it indicates the webclip is still referenced in a blueprint or active configuration and must be removed from those references before deletion can proceed. Devices that already have the webclip installed are not immediately affected by deletion from the library — the webclip remains on those devices until actively removed via an operation or blueprint change.
Key Fields
webclipId (path) — Esper webclip UUID (required)
Response — The deleted Webclip record
Common Use Cases
Removing an outdated or incorrect webclip from the tenant library Cleaning up test webclips created during development or blueprint configuration Decommissioning a webclip for a retired internal web application
Best Practices
If you receive a 409, use GET /api/v2/webclips/{webclipId} to confirm which blueprints and blueprint versions reference the webclip, then remove those references before retrying the delete
Store the returned Webclip record from the 200 response for audit trail purposes
Note that deletion removes the webclip from the console but does not uninstall it from devices where it is already deployed — use an uninstall operation for that
Path parameters
Response
Success
Example response
{
"content": {
"id": "09811f63-e2ca-4625-97c1-081145195d67",
"tenant_id": "7d5fd1bf-bdf9-490b-9e32-203756a61235",
"label": "Google",
"url": "https://www.google.com/",
"target_bundle_name": "Esper",
"target_bundle_id": "com.esper.io",
"is_removable": true
}
}