Splitwise · OAuth Scopes

Splitwise OAuth Scopes

OAuth 2.0 none

Splitwise uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from /oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyConsumerExpense ManagementPersonal FinanceBill SplittingPaymentsREST APIAuthentication
Scopes: 0 Flows: authorizationCode Method: none

OAuth endpoints

Authorization URL
/oauth/authorize
Token URL
/oauth/token
Flows
authorizationCode

Scopes (0)

Splitwise implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-10-14'
method: none
source: openapi/splitwise-comments-api-openapi.yml, openapi/splitwise-expenses-api-openapi.yml,
  openapi/splitwise-friends-api-openapi.yml, openapi/splitwise-groups-api-openapi.yml, openapi/splitwise-notifications-api-openapi.yml,
  openapi/splitwise-other-api-openapi.yml, openapi/splitwise-users-api-openapi.yml
schemes:
- name: OAuth
  source: openapi/splitwise-comments-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-expenses-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-friends-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-groups-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-notifications-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-other-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
- name: OAuth
  source: openapi/splitwise-users-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: |-
    Splitwise uses OAuth 2 with the authorization code flow. To connect via OAuth 2, you'll need to [register your app](https://secure.splitwise.com/apps). When you register, you'll be given a key and secret.

    **Note**: OAuth can be a very confusing protocol to implement correctly, and we **strongly** recommend
    that you use an existing OAuth library to connect to Splitwise. You can find a list of OAuth client libraries at the
    [OAuth community site](https://oauth.net/code/#client-libraries).

    For more information on using OAuth, check out the following resources:

    - The OAuth community [getting started guide](https://oauth.net/getting-started/)
    - The oauth.com [OAuth 2.0 playground](https://www.oauth.com/playground/) (great for debugging authorization issues)
    - This [old Splitwise blog post](https://blog.splitwise.com/2013/07/15/setting-up-oauth-for-the-splitwise-api/) about OAuth
scopes: []
note: The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement
  references one.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/splitwise-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.