curl --fail-with-body -X DELETE "https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN" -iconst res = await fetch('https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode', {
method: 'DELETE',
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
// 204 whether or not you held the mode — releasing twice is not an error.
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/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
if res.status_code != 204:
body = res.json()
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
package main
import (
"fmt"
"log"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest(http.MethodDelete, "https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode", 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()
fmt.Println(res.StatusCode) // 204
}
Stop pricing this listing
Hand the listing back to Maat’s own pricing.
Your rate rows are kept — they are your submission and your record of what you quoted, and a re-take resumes on them. What changes is that they stop being read.
The listing’s own pricing rules are not switched back on. Taking the mode turned them off; the host decides which to re-enable, because auto-restoring would revive rules they may have been glad to see go.
Owner only, and idempotent: releasing a listing you do not price answers 204
just the same. The host can also release from the Maat app at any time, and
does not need your agreement to do it.
Live in a sandbox workspace. Returns 501 against a production one, where no
mode is released.
curl --fail-with-body -X DELETE "https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN" -iconst res = await fetch('https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode', {
method: 'DELETE',
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
// 204 whether or not you held the mode — releasing twice is not an error.
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/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
if res.status_code != 204:
body = res.json()
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
package main
import (
"fmt"
"log"
"net/http"
"os"
)
func main() {
req, _ := http.NewRequest(http.MethodDelete, "https://maatstays.wtf/v1/listings/7c4b1e58-2a90-4f61-b3d2-5e8a1c0f7d24/pricing-mode", 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()
fmt.Println(res.StatusCode) // 204
}
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 listing.
Response
The listing is back on Maat's own pricing.