Sweep Connect

Sweep Connect lets your users connect Gmail, Google Drive, Outlook, OneDrive or Dropbox to Sweep without you building provider OAuth, token storage, consent screens or capability UX.

1. POST /v1/connect/sessions with your end_user_ref, the providers, the operation classes you need and a redirect_uri.
2. Send the user to the returned hosted url (https://trustysweep.com/connect/…). It works on desktop and mobile; a return deep link is supported.
3. The user picks providers, sees exactly what each operation class allows, and consents. Provider OAuth runs inside Sweep.
4. The user returns to your redirect_uri with ?session=…. GET /v1/connect/sessions/{id} gives you the connection_id.
5. Use connection_id on every call. You never receive a Google, Microsoft or Dropbox token.

Consent tiers

Tier	Operation classes	Step-up
1	discover, monitor	no
2	preserve, write, restore	write/restore require an explicit step
3	remove, migrate, automate, billable_execute	always an explicit step, per class

A connection created for discover cannot silently become destructive: request broader classes with POST /v1/connections/{id}/step-up; the user re-consents.

Revocation

Users can revoke your connection from their account at any time; you can revoke with POST /v1/connections/{id}/revoke. Revocation halts execution immediately and emits sweep.connection.revoked.

Test mode

With a sk_test_ key the hosted flow uses the simulated provider and completes without a real provider login, so you can test the whole loop in CI.