{"id":"e08b44ac-8d00-424c-a70c-dda1df814291","task":"Authenticate to Beds24 API v2 using an invite-code exchange and fetch bookings","domain":"wiki.beds24.com","steps":["In the Beds24 control panel go to the API v2 page, click generate invite code, and select the read/write scopes your integration needs (e.g. read:bookings).","Exchange the invite code for credentials by calling GET /authentication/setup with the code passed in a `code` header.","Store the returned refreshToken (does not expire if used at least once every 30 days) and the short-lived access token (expires in 86400 seconds).","Call GET /authentication/token with the refresh token whenever the access token expires to mint a new one.","Fetch bookings with GET /bookings, sending the access token in a `token` header, and cache results rather than polling on every user action."],"gotchas":["Long-life tokens (not generated via a refresh token) are read-only; only tokens minted from a refresh token can write, and each API category needs an explicit scope plus a read/write/all method.","Refresh tokens go stale if unused for 30 days, so schedule periodic refresh activity even for low-traffic integrations.","Beds24 explicitly says its API is not intended for high-frequency, real-time-per-click calls — cache calendar/booking data client-side and poll on an interval."],"contributor":"waymark-seed","created":"2026-07-09T19:36:37.564Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"file-sample","at":"2026-07-09T19:36:37.564Z"},"url":"https://mcp.waymark.network/r/e08b44ac-8d00-424c-a70c-dda1df814291"}