Delete records securely. With built-in safety checks to prevent accidental deletion of dependent data.
DELETE /xpanel/xoport/Delete/JSON/{entity}/{id}Delete/JSON/ accept only the HTTP method DELETE. Any other method will result in the interface responding with ` 405 METHOD_NOT_ALLOWED ` and the header field ` Allow: DELETE `—before anything else happens. Please check your connection: Previously, the method was not checked here; a call using ` GET ` would also have deleted the data. If your program uses ` GET ` or ` POST`, please switch it to ` DELETE `.| Endpoint | Description | Scope | Safety Checks |
|---|---|---|---|
DELETE /Delete/JSON/product/{id} | Delete Product | products:delete | - |
DELETE /Delete/JSON/category/{id} | Delete category | categories:delete | Subcategories, Products |
DELETE /Delete/JSON/customer/{id} | Delete customer | customers:delete | Orders |
DELETE /Delete/JSON/manufacturer/{id} | Delete manufacturer | manufacturers:delete | Products |
DELETE /Delete/JSON/newsdesk/{id} | Delete News Article | news:delete | - |
DELETE /Delete/JSON/newsdeskcat/{id} | Delete a news category | newscategories:delete | Subcategories, Articles |
DELETE /Delete/JSON/faq/{id} | Delete FAQ | faq:delete | - |
DELETE /Delete/JSON/faqcategory/{id} | Delete FAQ Category | faqcategories:delete | FAQ Entries |
DELETE /Delete/JSON/seohistory/{id} | Delete SEO History | seohistory:delete | Bulk Delete, Filter, Expired |
DELETE /Delete/JSON/newsletter_subscriber/{id} | Delete Newsletter Subscriber | newsletter:delete | GDPR Cascade, Provider Sync, Bulk Delete |
DELETE /Delete/JSON/newsletter/{id} | Delete newsletter campaign | newsletters:delete | Locked Check, Sent Check (409) |
DELETE /Delete/JSON/ticket/{id} | Delete Ticket NEW | tickets:delete | Cascade: History, Admins, Followers, Events, Files |
| Media NEW v2.16.0 | DELETE /Delete/JSON/media/{id} | media:delete | |
| Slider NEW v2.22.0 | DELETE /Delete/JSON/slider/{id} |
slider:delete |
|
DELETE /Delete/JSON/project/{id} | Delete xoCRM Project NEW v2.35.0 | projects:delete | Cascade: Tasks, Descriptions, Managers, Customers, Categories, Status History; Orders/Tickets are only decoupled |
DELETE /Delete/JSON/project_task/{id} | Delete Project Task NEW v2.35.0 | project_tasks:delete | Cascade: Descriptions, Assignees, Clients, Categories, Status History (project remains) |
DELETE /Delete/JSON/appointment/{id} | Delete Appointment (Soft Delete) NEW v2.44.0 | appointments:delete | Sets `deleted_at` (CalDAV tombstone); descriptions and links are preserved |
DELETE /Delete/JSON/order_status_history/{id} | Delete an order history entry NEW v2.95.0 | orders:write | Order status is updated; oldest entry is protected (409) |
DELETE /Delete/JSON/ticket_status_history/{id} | Delete a ticket history entry NEW v2.95.0 | tickets:delete | Ticket status is updated |
DELETE /Delete/JSON/ticket_attachment/{tshid}?filename=… | Remove a ticket attachment NEW v2.97.0 | tickets:delete | File only if no other entry refers to it |
DELETE /Delete/JSON/ticket_department/{id} | Delete ticket department NEW v2.103.0 | tickets:delete | Used: 409 – ?reassign_to={id} or ?force=1 |
Certain resources cannot be deleted if dependent data exists:
HAS_SUBCATEGORIES: Has subcategoriesHAS_PRODUCTS: Contains productsHAS_SUBCATEGORIES: Has subcategoriesHAS_ARTICLES: Contains news articlesHAS_ORDERS: Has orders{
"success": true,
"deleted_id": 23,
"details": {
"newsdesk_id": 23,
"newsdesk_article_name": "Gelöschter Artikel"
}
}{
"success": false,
"error": {
"code": "HAS_SUBCATEGORIES",
"message": "Cannot delete newsdesk category \"Shopnews\" (ID: 1): Has 3 sub-categories. Delete them first."
}
}Delete operations are irreversible. First, create an export as a backup.
Create an exportThe import endpoints enable efficient data import from external systems. Thanks to intelligent upsert logic, you don’t have to worry about distinguishing between new and existing records.
errors` array in the response for failed recordsYour shopping cart is empty.
