curl --fail-with-body "https://maatstays.wtf/v1/finance/payouts/upcoming" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"const res = await fetch('https://maatstays.wtf/v1/finance/payouts/upcoming', {
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.code}: ${body.detail}`);
for (const row of body.items) {
console.log(row.available_on, row.amount.value, row.amount.currency, row.bookings);
}
import os
import requests
res = requests.get(
"https://maatstays.wtf/v1/finance/payouts/upcoming",
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')}")
for row in body["items"]:
print(row["available_on"], row["amount"]["value"], row["bookings"])
package main
import (
"encoding/json"
"fmt"
"log"
"net/http"
"os"
)
type money struct {
Value string `json:"value"`
Currency string `json:"currency"`
}
type upcoming struct {
AvailableOn string `json:"available_on"`
Amount money `json:"amount"`
Bookings int `json:"bookings"`
}
type list struct {
Items []upcoming `json:"items"`
}
func main() {
req, _ := http.NewRequest(http.MethodGet,
"https://maatstays.wtf/v1/finance/payouts/upcoming", 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()
var body list
if err := json.NewDecoder(res.Body).Decode(&body); err != nil {
log.Fatal(err)
}
if res.StatusCode >= 400 {
log.Fatalf("upcoming failed: %d", res.StatusCode)
}
for _, u := range body.Items {
fmt.Println(u.AvailableOn, u.Amount.Value, u.Amount.Currency, u.Bookings)
}
}
{
"items": [
{
"available_on": "2026-09-12",
"amount": {
"value": "4100.00",
"currency": "EGP"
},
"bookings": 1
},
{
"available_on": "2026-09-30",
"amount": {
"value": "640.00",
"currency": "USD"
},
"bookings": 2
}
]
}See what is due to be released
The escrowed money on its way to you, grouped by the date it is released and the currency it settled in.
Funds are released when the stay starts, so available_on is a check-in date and
the whole answer is in the future. Only stays you have CONFIRMED are counted: a
request nobody has answered is not money on its way.
One row is one date AND one currency. Two currencies releasing on the same day are
two rows, and the currency is on amount.
This list is not paged. It is bounded by the platform rather than by your history — future release dates on confirmed stays only — so a page parameter would suggest an unbounded set and invite a walk of one.
Live in a sandbox workspace. Returns 501 against a production one. A sandbox
never charges anybody, so it answers an empty list.
curl --fail-with-body "https://maatstays.wtf/v1/finance/payouts/upcoming" \
-H "Authorization: Bearer $MAAT_PARTNER_TOKEN"const res = await fetch('https://maatstays.wtf/v1/finance/payouts/upcoming', {
headers: { Authorization: `Bearer ${process.env.MAAT_PARTNER_TOKEN}` },
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.code}: ${body.detail}`);
for (const row of body.items) {
console.log(row.available_on, row.amount.value, row.amount.currency, row.bookings);
}
import os
import requests
res = requests.get(
"https://maatstays.wtf/v1/finance/payouts/upcoming",
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')}")
for row in body["items"]:
print(row["available_on"], row["amount"]["value"], row["bookings"])
package main
import (
"encoding/json"
"fmt"
"log"
"net/http"
"os"
)
type money struct {
Value string `json:"value"`
Currency string `json:"currency"`
}
type upcoming struct {
AvailableOn string `json:"available_on"`
Amount money `json:"amount"`
Bookings int `json:"bookings"`
}
type list struct {
Items []upcoming `json:"items"`
}
func main() {
req, _ := http.NewRequest(http.MethodGet,
"https://maatstays.wtf/v1/finance/payouts/upcoming", 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()
var body list
if err := json.NewDecoder(res.Body).Decode(&body); err != nil {
log.Fatal(err)
}
if res.StatusCode >= 400 {
log.Fatalf("upcoming failed: %d", res.StatusCode)
}
for _, u := range body.Items {
fmt.Println(u.AvailableOn, u.Amount.Value, u.Amount.Currency, u.Bookings)
}
}
{
"items": [
{
"available_on": "2026-09-12",
"amount": {
"value": "4100.00",
"currency": "EGP"
},
"bookings": 1
},
{
"available_on": "2026-09-30",
"amount": {
"value": "640.00",
"currency": "USD"
},
"bookings": 2
}
]
}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.
Response
What is due to be released, by date and currency.
One row per release date and currency, soonest first. Not paged: the set is bounded by the platform, not by your history.
Show child attributes
Show child attributes