Update a listing
Aufruf, Parameter, Antwort und Fehler von PATCH /v1/listings/{externalListingId}.
Zuletzt aktualisiert:
A JSON Merge Patch (RFC 7396) of the OpenImmo 2.0 listing: a member that is missing stays, null clears it. media: [] or null removes the files that came through the API, contact: null removes the contact person. Cannot be cleared: data.distributionType, data.estateType. A running listing blocks changing the address parts or the distribution type (409 listing_active). Needs write access to listings.
Braucht den Scope propose.
Aufruf
PATCH https://api.athaus.ai/v1/listings/{externalListingId}Parameter
Pfad
| Name | Typ | Pflicht | Beschreibung |
|---|---|---|---|
externalListingId | string | ja | 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. |
Kopf
| Name | Typ | Pflicht | Beschreibung |
|---|---|---|---|
Athaus-Version | string | nein | 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 | nein | Only if the current ETag of the resource is listed (or *: only if the resource exists). Otherwise 412 and nothing is written. |
Rumpf
JSON mit Content-Type: application/json. Ein Feld, das die API nicht kennt, ist ein 400, und errors[].name nennt das Feld. Der Rumpf ist Pflicht.
| Feld | Typ | Beschreibung |
|---|---|---|
data | object | any | |
metadata | object | any | |
userDefined | object[] | any | |
media | object[] | any | |
contact | object | any |
Beispiel
curl -X PATCH "https://api.athaus.ai/v1/listings/WE-12" \
-H "Authorization: Bearer ath_live_..." \
-H "Content-Type: application/json" \
-d '{"data":{"prices":{"buy":{"price":{"amount":340000}}}}}'Antwort
Bei Erfolg kommt 202 mit ListingReceipt.
ListingReceipt
| Feld | Typ | Beschreibung |
|---|---|---|
requestId | string | |
listingId | string | |
externalListingId | string | |
warnings | object[] | |
warnings[].type | string | |
warnings[].message | string |
Köpfe der Antwort
| Kopf | Beschreibung |
|---|---|
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. |
Fehler
Jeder Fehler kommt als Problem Details. Verzweige auf code, nicht auf title oder detail.
| Status | Codes | Bedeutung |
|---|---|---|
400 | api_version_unsupported, invalid_input, invalid_body, profile_unsupported | 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 | address_already_exists | 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. |
413 | payload_too_large | The request body is larger than 512 KB. |
415 | invalid_input | The request body is not JSON. Send Content-Type: application/json. |
429 | rate_limited | Rate limit exceeded. |
500 | internal_error | Server error. |
Weiter lesen
REST-API: Anmeldung mit einem API-Key
Jeder Aufruf von /v1 trägt einen API-Key als Bearer-Token. Wo du ihn bekommst, welche Scopes er trägt und was nicht geht.
REST-API: Fehler als Problem Details
Jeder Fehler von /v1 ist ein Problem nach RFC 9457 mit echtem HTTP-Status, einem Code zum Verzweigen und einer Request-Id für den Support.