curl --fail-with-body "https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"
const res = await fetch('https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d', {
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.code}: ${body.detail}`);
console.log(body.status, body.stay.check_in, body.console_url);
import os
import requests
res = requests.get(
"https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
body = res.json()
if res.status_code >= 400:
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
print(body["status"], body["stay"]["check_in"], body["console_url"])
package main
import (
"encoding/json"
"fmt"
"log"
"net/http"
"os"
)
type payload struct {
Status string `json:"status"`
ConsoleURL string `json:"console_url"`
}
func main() {
req, _ := http.NewRequest(http.MethodGet,
"https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d", 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()
if res.StatusCode >= 400 {
log.Fatalf("read failed: %d", res.StatusCode)
}
var body payload
if err := json.NewDecoder(res.Body).Decode(&body); err != nil {
log.Fatal(err)
}
fmt.Println(body.Status, body.ConsoleURL)
}
Read one booking
One booking. Addressed by Maat’s own booking_reference — the id every later
event about it carries.
404 booking_not_found is ONE answer for “no such booking” and “not in your
workspace” — telling them apart would confirm the existence of another
workspace’s reservation.
A 403 on this operation carries one of two codes — insufficient_scope (the
key lacks bookings:read) or workspace_scope_mismatch (a sandbox/production
mismatch). Branch on code.
Live in a sandbox workspace. Returns 501 against a production one.
curl --fail-with-body "https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"
const res = await fetch('https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d', {
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.code}: ${body.detail}`);
console.log(body.status, body.stay.check_in, body.console_url);
import os
import requests
res = requests.get(
"https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d",
headers={"Authorization": f"Bearer {os.environ['MAAT_PARTNER_TOKEN']}"},
timeout=30,
)
body = res.json()
if res.status_code >= 400:
raise RuntimeError(f"{body['code']}: {body.get('detail')}")
print(body["status"], body["stay"]["check_in"], body["console_url"])
package main
import (
"encoding/json"
"fmt"
"log"
"net/http"
"os"
)
type payload struct {
Status string `json:"status"`
ConsoleURL string `json:"console_url"`
}
func main() {
req, _ := http.NewRequest(http.MethodGet,
"https://maatstays.wtf/v1/bookings/5f3a91c2-e8b4-4a71-9c30-1e2f3a4b5c6d", 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()
if res.StatusCode >= 400 {
log.Fatalf("read failed: %d", res.StatusCode)
}
var body payload
if err := json.NewDecoder(res.Body).Decode(&body); err != nil {
log.Fatal(err)
}
fmt.Println(body.Status, body.ConsoleURL)
}
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 own id for the booking.
Response
The booking.
One booking, as your workspace reads it.
There is NO guest identity here, anywhere: no name, no initial, no email, no
phone, no reference you could join against another read. Every field is a fact
about a STAY, not a fact about a person. console_url is the honest pointer to
where a person IS seen — the host console, where an authenticated human sees who
is arriving. That is deliberately slower than a field on this wire, and it is the
point.
There is no cancellation over this API. Cancelling a confirmed stay creates refunds and penalties and belongs to a person in the app.
Maat's own booking id, and the correlation key for every later event. Treat it as OPAQUE: store it and echo it back, but do not parse it or derive anything from its shape. It is a UUID today and the contract does not promise it always will be.
Which of your inventory was booked. One object rather than four ids at the root, so that the same accessor reads a booking, a booking event and a publication event.
Show child attributes
Show child attributes
What was sold. This contract manages unit stays; a write against the other two is refused with inventory_not_supported.
See InventoryKind.
unit, service, experience A closed vocabulary, not the platform's internal state. pending is the
only state confirm and reject act on.
See BookingStatus.
pending, confirmed, checked_in, completed, cancelled, rejected The stay itself — when, and how many people. Never who.
The two door times are the UNIT's own, for a booking whose
inventory_kind is unit. A service or an experience hangs off no
unit and has no door: those bookings carry the platform defaults (15:00 /
12:00) so the field is always present and always a real time, and an
integration that staffs a door should branch on inventory_kind rather than
treat them as the operator's own answer.
Show child attributes
Show child attributes
What the guest paid, as one object. null when it cannot be stated — a
legacy row with no recorded amount resolves to null, never to "0.00":
zero would read as free, and null means "we do not know".
Show child attributes
Show child attributes
True when the listing takes bookings without the host approving each one.
Present only on a cancelled booking.
Show child attributes
Show child attributes
When the booking was created in Maat.
The host console's page for this booking — where a person is seen.