Delete a sales / lease / exchange

​

Headers

​

Path parameters

​

Auth requirements

​

What happens, in order

1. Listing is fetched and ownership checked. Otherwise 404.
2. listing.deleted audit row written with key fields snapshotted in previous_state (title, msn, listing_type, status, country).
3. Every URL in documents[] and images[] is parsed and best-effort deleted from Supabase Storage. Individual failures are logged but don’t fail the call.
4. The listing row is hard-deleted from the database in the same transaction as the audit write.
5. 204 No Content returned.

​

Response

curl -X DELETE "$base_url/public/v1/sales-lease-exchange/$listing_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id"

import requests
resp = requests.delete(
    f"{base_url}/public/v1/sales-lease-exchange/{listing_id}",
    headers={"Authorization": f"Bearer {api_key}", "X-Organization-Id": org_id},
)
if resp.status_code == 204:
    print("Deleted")
elif resp.status_code == 404:
    print("Not found (or not yours)")
else:
    resp.raise_for_status()

HTTP/1.1 204 No Content

{ "detail": "Listing not found" }

​

Soft-delete alternative

curl -X PATCH "$base_url/public/v1/sales-lease-exchange/$listing_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id" \
  -H "Content-Type: application/json" \
  -d '{"status": "archived"}'

​

See also

• Update for the soft-delete-via-PATCH pattern.
• Errors for the 404 semantics.