---
title: "Settle Split"
method: PUT
path: "/api/partners/splits/{split_id}/settle"
tags: ["Partners"]
---

# Settle Split

`PUT /api/partners/splits/{split_id}/settle`

## Request

- Base URL: `https://api.earmarkiq.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.earmarkiq.app/api/partners/splits/{split_id}/settle`
- Auth: HTTP bearer

Mark a bill split as squared up between the two of you.

Settling is a bookkeeping fact, not a movement of money. earmarkIQ
cannot make a transfer between two people's banks and cannot reliably
observe one, so the only thing it can honestly record is that the two
of you consider this settled — which removes the row from the
outstanding balance and nothing else.

It deliberately does NOT touch budget spend: _calculate_partner_spend
sums what each person actually spent, and a transfer between partners
is not spending by either of them. Matching a settlement to a real
bank transfer would need partner-to-partner transfer detection and is
a separate piece of work.

## Path parameters

- `split_id` string, uuid, required

## Response `200`

Successful Response

- SplitBillResponse
  - `id` string, required
  - `description` string, required
  - `total_amount` number, required
  - `split_type` string, required
  - `user1_share` number, required
  - `user2_share` number, required
  - `settled` boolean, required
  - `created_at` string, required
  - `settled_at` string, nullable, required
  - `you_paid` boolean, nullable, required
  - `your_share` number, required
  - `their_share` number, required
  - `transaction_id` string, nullable, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/earmarkiq/apis/earmark-api.md) · [All operations](https://skmtc.dev/earmarkiq/apis/earmark-api/llms.txt) · [OpenAPI document](https://skmtc.dev/earmarkiq/apis/earmark-api/revisions/4a2c41907105?raw)