Multi-tenant Xero on Lovable Cloud (TanStack Start + Lovable Cloud Postgres) — each customer connects their own Xero organisation and the app acts as that customer. Covers OAuth 2 (authorize → callback → refresh) with rotating refresh tokens, per-user encrypted token storage, scope selection (granular > broad), idempotent writes, sibling-row refresh, reconnect UX, and the Lovable-specific traps around iframe preview, host mapping, and redirect URIs.
Connect ONE Xero organisation that you own to a Lovable Cloud (TanStack Start + Lovable Cloud Postgres) app, so every visitor sees the same books through your single connection. Covers OAuth 2 (authorize → callback → refresh) with rotating refresh tokens, encrypted token storage, scope selection (granular > broad), idempotent writes, and the Lovable-specific traps around iframe preview, host mapping, and redirect URIs.
Build a MULTI-TENANT Xero integration in PYTHON where EACH end user of the app connects THEIR OWN Xero organisation, with their own access + refresh tokens. Use whenever building a multi-tenant Python SaaS on Xero (Flask, FastAPI, Django, etc.) — every customer authorizes their own Xero and the app acts as that customer. Covers the OAuth2 + PKCE consent leg with an OAuth client (Authlib), the official `xero-python` SDK for API calls and refresh, per-user encrypted token storage, the global token getter/saver trap, refresh/rotation, tenant selection, scopes (including the granular-scope migration), and the Xero API gotchas that bite in production (date/money/tax normalisation, idempotent writes, rate limits). Read this BEFORE writing any multi-tenant Xero code in Python. If instead the app talks to a SINGLE Xero org that the builder owns, do NOT use this flow — see "Do you actually need this?" at the top for the much simpler single-tenant approach. For a JavaScript/TypeScript app, use the `xero-integration-mul
Build a MULTI-TENANT Xero integration where EACH end user of the app connects THEIR OWN Xero organisation, with their own access + refresh tokens. Use whenever building a multi-tenant SaaS on Xero — every customer authorizes their own Xero and the app acts as that customer. Covers the full OAuth2 + PKCE lifecycle with the official `xero-node` SDK, per-user encrypted token storage, refresh/rotation, tenant selection, scopes (including the granular-scope migration), and the Xero API gotchas that bite in production (date/money/tax normalisation, idempotent writes, rate limits). Read this BEFORE writing any multi-tenant Xero code. If instead the app talks to a SINGLE Xero org that the builder owns, do NOT use this flow — see "Do you actually need this?" at the top for the much simpler single-tenant approach.