splitwise_update_user
Update your Splitwise profile by changing first name, last name, locale, or default currency; email and password cannot be changed here.
Instructions
Update your Splitwise profile: first name, last name, locale and/or default currency.
Calls POST /update_user/{id} with only the fields you pass (at least one). This is
a write: it is refused with Error: … writes are disabled unless
SPLITWISE_ALLOW_WRITES=1. Email and password are NOT updatable on purpose — the
input has no such fields and the server's client refuses to send them under any
configuration, so an LLM can never change the account's login. There is no undo tool:
to revert, read the current values first with splitwise_get_current_user and call
this tool again with them.
When to Use:
To fix a typo in your name, or switch the default currency / interface locale.
When NOT to Use:
To change email or password (impossible here by design — do it at https://secure.splitwise.com).
To read your profile (use
splitwise_get_current_user).To rename a friend or group member (Splitwise does not allow editing other users).
Returns:
A confirmation naming the user Splitwise returned and, for each field you sent, the
value as it appears in the response. It is headed "Profile updated" only when every
sent field comes back with exactly the value sent. Otherwise it is headed "Update
accepted by Splitwise — N of M field(s) not confirmed" with those fields flagged, and
tells you to read the profile back with splitwise_get_current_user. This is common
for locale/default_currency, which the flat user object in the response may omit.
Examples:
params = {"user_id": 491923, "default_currency": "PEN"}params = {"user_id": 491923, "first_name": "Ada", "last_name": "Lovelace", "locale": "es"}
Error Handling:
Validation rejects a call with no field to change, an unknown field (including
email/password) or a currency that is not a 3-letter code, before any request.
locale is checked for format only and passed through; Splitwise decides whether it
is supported (a value it ignores shows as 'differs' in the confirmation).
403 when user_id is not your own id; 400 with Splitwise's field messages for a value
it rejects. A timeout or 5xx leaves the outcome UNKNOWN — read the profile back with
splitwise_get_current_user before retrying.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |