SaveSlot Docs

Developers

OAuth apps

An OAuth app lets people connect your product to their own SaveSlot account, the same way they connect Claude or ChatGPT. They choose which slots your app can reach, can change that later, and can revoke it under Connect agents.

Register an app

  1. In the console, open Developers → OAuth apps.
  2. Enter your app's name and its redirect URL. The redirect URL must use https://. For development, http://localhost and http://127.0.0.1 are accepted.
  3. Choose Register app. The console shows the app's client id.

Delete an app from the same list. People who authorized it lose the connection.

The authorization flow Draft

SaveSlot follows OAuth 2.1 with PKCE:

  1. Your app sends the person to the consent screen:
https://app.saveslot.ai/oauth/authorize
  ?client_id=ss_app_…
  &redirect_uri=https://yourapp.example/callback
  &response_type=code
  &state=…
  &code_challenge=…&code_challenge_method=S256
  1. The person signs in if needed, sees your app's name, your redirect domain and what you will get, and allows or denies.
  2. SaveSlot redirects to your redirect_uri with code and state. A denial returns error=access_denied.
  3. Your backend exchanges the code at POST https://api.saveslot.ai/v1/oauth/token with the code_verifier, and receives an access token and a refresh token.

What the person approves

The consent screen uses the same choices as for agents: all slots or selected slots, read only or read and write per slot, and whether your app may create tables or delete data. Your app can request a narrower starting point; the person can always narrow it further. See Agent permissions.

Open questions Draft