source identifies the connected data source, for example icloud_notes. scopes identify approved data sets, for example ["icloud_notes.notes"].
Start with a source that Vana Account already exposes on app.vana.org/sources. For the current supported source and scope list, see the data-connectors scope registry: PDP-Connect/data-connectors/SCOPES.md.
Request every scope in one approval. A grant is keyed by the (user, app) pair — not by scope — and re-approving replaces the grant’s scopes rather than adding to them. Put every scope your app needs in the scopes array of a single request so one approval covers them all. If you request scopes across separate approvals, the grant ends up holding only the most recently approved set, and reads for the dropped scopes start failing the scope check.Keep a request to a single source (current limitation). A request targets one source. Requesting scopes that span multiple sources in the same request — e.g. an icloud_notes.* scope together with a spotify.* scope — isn’t supported today: the approval connects only the one source, and a first-time user hasn’t connected the others yet, so those scopes read empty. If your app needs more than one source, drive each source’s approval separately for now.
