curl --fail-with-body -X DELETE https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94 \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"const res = await fetch(
'https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94',
{
method: 'DELETE',
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
},
);
// 204 whether or not it was still there — safe to retry.
if (res.status !== 204) {
const body = await res.json();
throw new Error(`${body.code}: ${body.detail}`);
}
import os
import requests
res = requests.delete(
"https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7"
"/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
# 204 whether or not it was still there — safe to retry.
if res.status_code != 204:
body = res.json()
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
package main
import (
"log"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest(http.MethodDelete,
"https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7"+
"/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94",
nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("MAAT_PARTNER_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
// 204 whether or not it was still there — safe to retry.
if res.StatusCode != http.StatusNoContent {
log.Fatalf("delete failed: %d", res.StatusCode)
}
}
Remove a photo
Removes the photo and closes the gap behind it, so positions stay dense.
If you delete the cover, position 0 of what remains becomes the cover. That is the same rule the Maat apps follow.
204 whether or not the photo was still there. Deleting something already gone
is the end state you asked for, so a retried or redelivered call is safe.
Deleting a photo never takes a listing off sale, even if the property drops
below the photo floor as a result — that would be a change you did not ask for.
Nor does any photo operation put one ON sale: publication is
PATCH /v1/listings/{listing_id} with status: "listed", which is where the
validity gate runs. GET /properties/by-id/{property_id} reports what the
property is missing at any time.
A property you create with PUT /properties/{provider_id} is refused with
409 conflict — your next push would undo the change. Send its photo URLs on the
push instead.
Live in a sandbox workspace. Returns 501 against a production one.
curl --fail-with-body -X DELETE https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94 \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"const res = await fetch(
'https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94',
{
method: 'DELETE',
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
},
);
// 204 whether or not it was still there — safe to retry.
if (res.status !== 204) {
const body = await res.json();
throw new Error(`${body.code}: ${body.detail}`);
}
import os
import requests
res = requests.delete(
"https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7"
"/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
# 204 whether or not it was still there — safe to retry.
if res.status_code != 204:
body = res.json()
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
package main
import (
"log"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest(http.MethodDelete,
"https://maatstays.wtf/v1/properties/3c9d1f42-7b60-4a18-9e55-0d2a6f8c31b7"+
"/photos/0f2b9c81-4a7e-4d33-9b10-2c7e5a6f1d94",
nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("MAAT_PARTNER_TOKEN"))
res, err := http.DefaultClient.Do(req)
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
// 204 whether or not it was still there — safe to retry.
if res.StatusCode != http.StatusNoContent {
log.Fatalf("delete failed: %d", res.StatusCode)
}
}
Authorizations
A short-lived partner token, obtained by exchanging your API key at
POST /token. Send it as Authorization: Bearer <access_token>.
Tokens live for fifteen minutes by default and never for more than an hour. Mint one per batch of work, not one per request.
The token carries the workspace and the environment its key was issued for. You cannot change either by asking: the exchange ignores everything in the request body for exactly that reason.
It also carries the key's scopes (scope, a list). Every operation names a
scope as x-maat-scope, and a token whose key lacks it is refused with
403 insufficient_scope, naming the scope. Scopes are fixed when a key is
issued and are re-read from the key on every request, so a key narrowed today is
narrowed on its next call — the token's scope is what the key held at exchange
time, for your own reading, never what authorizes a request.
x-maat-scope is the floor, and on the quick-action operations it is not the
whole requirement. PUT and DELETE /listings/{listing_id}/quick-actions/{template_key}
carry rules:write, and additionally require pricing:write when
template_key begins pricing. — the capability depends on the template in
the path, because a cleaning fee changes what a guest pays and a minimum stay
does not. The refusal is the same 403 insufficient_scope, naming
pricing:write. The two READS apply the same requirement without erroring:
GET /listings/{listing_id}/quick-actions still lists the pricing.* rows but
withholds their applied state, and GET /listings/{listing_id}/rules omits the
pricing rules entirely and reports pricing_withheld in warnings. These four
are the only operations in this document whose requirement is not exactly their
x-maat-scope, and each of them says so machine-readably:
x-maat-scope-additional lists the second scope it can require and
x-maat-scope-additional-when says what happens without it.
Never send it as a cookie or in a query string, and never store it — store the API key, mint tokens from it.
Path Parameters
Maat's identifier for the property, as returned by GET /properties. Not your
own provider_id — the write endpoint is the one keyed on that, which is why
this read carries a by-id segment.
Maat's identifier for one photo, as returned by
GET /properties/{property_id}/photos.
Response
The photo is gone.