Delete a listing
Request, parameters, response and errors of DELETE /v1/listings/{externalListingId}.
Last updated:
Removes the listing. Inquiries and their history stay readable; photos and documents go with it. Refused with 409 while a listing runs (listing_active), while a sole agency runs (brokerage_agreement_active) and while the listing has upcoming appointments (upcoming_viewings_exist): deleting would cancel them for the guests, and that is an action for a person. Needs write access to listings.
Requires the scope propose.
Request
DELETE https://api.athaus.ai/v1/listings/{externalListingId}Parameters
Path
| Name | Type | Required | Description |
|---|---|---|---|
externalListingId | string | yes | Your reference of the listing: the value of metadata.source.offererMarketingKey. A listing without one has its own listingId here, and the listingId always works in the path. 1 to 128 letters, digits, dots, underscores or hyphens, not starting or ending with a dot. |
Header
| Name | Type | Required | Description |
|---|---|---|---|
Athaus-Version | string | no | Optional and carries nothing a client needs: the version is the path. Accepted when it says v1 or 1. Any other value is a 400 api_version_unsupported. |
If-Match | string | no | Only if the current ETag of the resource is listed (or *: only if the resource exists). Otherwise 412 and nothing is written. |
Example
curl -X DELETE "https://api.athaus.ai/v1/listings/WE-12" \
-H "Authorization: Bearer ath_live_..."Response
On success the status is 202 with ListingReceipt.
ListingReceipt
| Field | Type | Description |
|---|---|---|
requestId | string | |
listingId | string | |
externalListingId | string | |
warnings | object[] | |
warnings[].type | string | |
warnings[].message | string |
Response headers
| Header | Description |
|---|---|
Request-Id | Identifies this request. Quote it in a support request. |
Athaus-Version | The API version of this response: v1. |
Athaus-Release | The release of v1 that answered, for example 1.0. A label for support and changelogs; no request can select it. |
RateLimit-Policy | The quota policy of the bucket that applies. |
RateLimit | Remaining quota and seconds until the bucket is full again. |
Errors
Every error arrives as problem details. Branch on code, not on title or detail.
| Status | Codes | Meaning |
|---|---|---|
400 | api_version_unsupported, invalid_input | Invalid request. |
401 | unauthorized | Missing or invalid API key. |
403 | insufficient_permissions, plan_required | The key lacks a right, or the plan does not include API access. |
404 | not_found | Nothing under this ID. |
409 | upcoming_viewings_exist, listing_active, brokerage_agreement_active | The request conflicts with the state of the resource (for example a duplicate), or with an idempotency key. |
412 | precondition_failed | The condition of If-Match (or If-None-Match) does not hold for the current state of the resource. Nothing was written. |
429 | rate_limited | Rate limit exceeded. |
500 | internal_error | Server error. |
Keep reading
REST API: authentication with an API key
Every call to /v1 carries an API key as a bearer token. Where to get one, which scopes it carries and what does not work.
REST API: errors as problem details
Every error from /v1 is an RFC 9457 problem with a real HTTP status, a code to branch on and a request id for support.