ClearList OAuth Scopes

generated: '2026-11-04'
method: derived
source: openapi/clearlist-me-openapi.json
schemes:
- name: oauth2
  source: openapi/clearlist-me-openapi.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://clearlist.me/oauth/authorize
    tokenUrl: https://clearlist.me/api/oauth/token
  description: 'OAuth 2.1 authorization code flow. PKCE with code_challenge_method=S256 is required;
    public clients only (token_endpoint_auth_method none). Access tokens are `cl_<64-hex>` and
    are sent as `Authorization: Bearer <token>` (X-ClearList-API-Key also works). Operations
    that change state require the `write` scope; a grant without it gets 403. Reading needs
    no specific scope, so a `write`-only grant can also read.'
scopes:
- scope: read
  description: Read listings, reservations, conversations, page stats and plan status.
  flows:
  - authorizationCode
  sources:
  - openapi/clearlist-me-openapi.json
- scope: write
  description: Create, edit, delete and publish listings; reply to buyers; share an address
    through the confirmed flow; set availability; create payment links.
  flows:
  - authorizationCode
  sources:
  - openapi/clearlist-me-openapi.json