Splitwise website screenshot

Splitwise

Splitwise is an expense-sharing and bill-splitting service that helps roommates, travel groups, couples, and friends track shared costs and settle up fairly. Its public Self-Serve REST API (v3.0) lets third-party applications read and manage a user's groups, friends, expenses, comments, and notifications on that user's behalf, authenticating with OAuth 2.0 or a personal API key. Splitwise was added to the API Evangelist network from a venture-capital portfolio lead and has been enriched from its public developer documentation and OpenAPI specification.

Splitwise publishes 7 APIs on the APIs.io network, including comments API, expenses API, friends API, and 4 more. Tagged areas include Company, Consumer, Expense Management, Personal Finance, and Bill Splitting.

Splitwise’s developer surface includes authentication, documentation, API reference, signup flow, engineering blog, and 21 more developer resources.

41.9/100 developing ▬ flat Agent 29/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs
CompanyConsumerExpense ManagementPersonal FinanceBill SplittingPaymentsREST APIAuthentication

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/splitwise: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Splitwise comments API

The comments API from Splitwise — 3 operation(s) for comments.

Splitwise expenses API

The expenses API from Splitwise — 6 operation(s) for expenses.

Splitwise friends API

The friends API from Splitwise — 5 operation(s) for friends.

Splitwise groups API

A Group represents a collection of users who share expenses together. For example, some users use a Group to aggregate expenses related to a home. Others use it to represent a t...

Splitwise notifications API

The notifications API from Splitwise — 1 operation(s) for notifications.

Splitwise other API

The other API from Splitwise — 2 operation(s) for other.

Splitwise users API

Resources to access and modify user information.

Scroll for all 7

Open Collections 8

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Splitwise comments API

OPEN COLLECTION

Scroll for all 8

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Splitwise Authentication

http/oauth2 · 2 schemes

SECURITY

Splitwise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Splitwise Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Splitwise Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: splitwise
name: Splitwise
description: Splitwise is an expense-sharing and bill-splitting service that helps roommates, travel groups, couples, and
  friends track shared costs and settle up fairly. Its public Self-Serve REST API (v3.0) lets third-party applications read
  and manage a user's groups, friends, expenses, comments, and notifications on that user's behalf, authenticating with OAuth
  2.0 or a personal API key. Splitwise was added to the API Evangelist network from a venture-capital portfolio lead and has
  been enriched from its public developer documentation and OpenAPI specification.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://www.splitwise.com/assets/press/logos/sw.svg
url: https://raw.githubusercontent.com/api-evangelist/splitwise/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bullpen-capital
- insight-partners
- matrix-partners
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Consumer
- Expense Management
- Personal Finance
- Bill Splitting
- Payments
- REST API
- Authentication
tags_raw:
- Company
- Consumer
- Expense Management
- Personal Finance
- Bill Splitting
- Payments
- REST API
- OAuth
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: splitwise:splitwise-comments-api
  name: Splitwise comments API
  description: The comments API from Splitwise — 3 operation(s) for comments.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - Comments
  tags_raw:
  - comments
  properties:
  - type: OpenAPI
    url: openapi/splitwise-comments-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-expenses-api
  name: Splitwise expenses API
  description: The expenses API from Splitwise — 6 operation(s) for expenses.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - Expenses
  tags_raw:
  - expenses
  properties:
  - type: OpenAPI
    url: openapi/splitwise-expenses-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-friends-api
  name: Splitwise friends API
  description: The friends API from Splitwise — 5 operation(s) for friends.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - Friends
  tags_raw:
  - friends
  properties:
  - type: OpenAPI
    url: openapi/splitwise-friends-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-groups-api
  name: Splitwise groups API
  description: A Group represents a collection of users who share expenses together. For example, some users use a Group to
    aggregate expenses related to a home. Others use it to represent a trip. Expenses assigned to a group are split among
    the users of that group. Importantly, two users in a Group can also have expenses with one another outside of the Group.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - Group
  tags_raw:
  - groups
  properties:
  - type: OpenAPI
    url: openapi/splitwise-groups-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-notifications-api
  name: Splitwise notifications API
  description: The notifications API from Splitwise — 1 operation(s) for notifications.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - Notification
  tags_raw:
  - notifications
  properties:
  - type: OpenAPI
    url: openapi/splitwise-notifications-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-other-api
  name: Splitwise other API
  description: The other API from Splitwise — 2 operation(s) for other.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags: []
  tags_raw:
  - other
  properties:
  - type: OpenAPI
    url: openapi/splitwise-other-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
- aid: splitwise:splitwise-users-api
  name: Splitwise users API
  description: Resources to access and modify user information.
  humanURL: https://dev.splitwise.com/
  baseURL: https://secure.splitwise.com/api/v3.0
  tags:
  - User
  tags_raw:
  - users
  properties:
  - type: OpenAPI
    url: openapi/splitwise-users-api-openapi.yml
  - type: Conventions
    url: conventions/splitwise-conventions.yml
  - type: ErrorCatalog
    url: errors/splitwise-problem-types.yml
  - type: DataModel
    url: data-model/splitwise-data-model.yml
common:
- type: Overlay
  url: overlays/splitwise-api-overlay.yaml
- type: Authentication
  url: authentication/splitwise-authentication.yml
- type: OAuthScopes
  url: scopes/splitwise-scopes.yml
- type: Conventions
  url: conventions/splitwise-conventions.yml
- type: ErrorCatalog
  url: errors/splitwise-problem-types.yml
- type: DataModel
  url: data-model/splitwise-data-model.yml
- type: Conformance
  url: conformance/splitwise-conformance.yml
- type: Lifecycle
  url: lifecycle/splitwise-lifecycle.yml
- type: StatusPage
  url: https://status.splitwise.com/
- type: Packages
  url: packages/splitwise-packages.yml
- type: X-MCPServerCandidate
  url: mcp/splitwise-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/splitwise-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/splitwise-well-known.yml
- type: SecurityTxt
  url: well-known/splitwise-security.txt
- type: VulnerabilityDisclosure
  url: security/splitwise-vulnerability-disclosure.yml
- type: Security
  url: security/splitwise-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/splitwise-domain-security.yml
- type: DeveloperPortal
  url: https://dev.splitwise.com/
- type: Documentation
  url: https://dev.splitwise.com/
- type: APIReference
  url: https://dev.splitwise.com/
- type: SignUp
  url: https://secure.splitwise.com/apps
- type: Blog
  url: https://blog.splitwise.com/
- type: TermsOfService
  url: https://www.splitwise.com/terms
- type: PrivacyPolicy
  url: https://www.splitwise.com/privacy
- type: Website
  url: https://www.splitwise.com
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 15
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/splitwise"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/splitwise/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/splitwise/evidence"

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.

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