Skip to content
Changelog

Report a bug

Splitwise integration: operations for AI agents

Splitwise connects to Type.com as an integration. This page lists the 27 operations documented for Claude and Codex in Type.com: 12 read, 10 write, 5 destructive.

About Splitwise

Splitwise helps you split bills and expenses with friends and family.

Categories: Finance & Accounting

How to connect Splitwise to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

27 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

27 operations listed.

Users

  • Read

    Get information about the current user

    GET /get_current_user

    GET /get_current_user

  • Read

    Get information about another user

    GET /get_user/{id}

    GET /get_user/{id}

  • Write

    Update a user

    POST /update_user/{id}

    POST /update_user/{id}

Groups

  • Read

    List the current user's groups

    Note: Expenses that are not associated with a group are listed in a group with ID 0.

    GET /get_groups

  • Read

    Get information about a group

    GET /get_group/{id}

    GET /get_group/{id}

  • Write

    Create a group

    Creates a new group. Adds the current user to the group by default. Note: group user parameters must be flattened into the format users{index}{property}, where property is userid, firstname, lastname, or email. The user's email or ID must be provided.

    POST /create_group

  • Write

    Restore a group

    Restores a deleted group. Note: 200 OK does not indicate a successful response. You must check the success value of the response.

    POST /undelete_group/{id}

  • Write

    Add a user to a group

    Note: 200 OK does not indicate a successful response. You must check the success value of the response.

    POST /add_user_to_group

  • Destructive

    Delete a group

    Delete an existing group. Destroys all associated records (expenses, etc.)

    POST /delete_group/{id}

  • Destructive

    Remove a user from a group

    Remove a user from a group. Does not succeed if the user has a non-zero balance. Note: 200 OK does not indicate a successful response. You must check the success value of the response.

    POST /remove_user_from_group

Friends

  • Read

    List current user's friends

    Note: group objects only include group balances with that friend.

    GET /get_friends

  • Read

    Get details about a friend

    GET /get_friend/{id}

    GET /get_friend/{id}

  • Write

    Add a friend

    Adds a friend. If the other user does not exist, you must supply userfirstname. If the other user exists, userfirstname and userlastname will be ignored.

    POST /create_friend

  • Write

    Add friends

    Add multiple friends at once. For each user, if the other user does not exist, you must supply users{index}firstname. Note: user parameters must be flattened into the format users{index}{property}, where property is firstname, lastname, or email.

    POST /create_friends

  • Destructive

    Delete friendship

    Given a friend ID, break off the friendship between the current user and the specified user. Note: 200 OK does not indicate a successful response. You must check the success value of the response.

    POST /delete_friend/{id}

Other

  • Read

    Supported currencies

    Returns a list of all currencies allowed by the system. These are mostly ISO 4217 codes, but we do sometimes use pending codes or unofficial, colloquial codes (like BTC instead of XBT for Bitcoin).

    GET /get_currencies

  • Read

    Supported categories

    Returns a list of all categories Splitwise allows for expenses. There are parent categories that represent groups of categories with subcategories for more specific categorization. When creating expenses, you must use a subcategory, not a parent category. If you intend for an expense to be represented by the parent category and nothing more specific, please use the "Other" subcategory.

    GET /get_categories

Expenses

  • Read

    Get expense information

    GET /get_expense/{id}

    GET /get_expense/{id}

  • Read

    List the current user's expenses

    GET /get_expenses

    GET /get_expenses

  • Write

    Create an expense

    Creates an expense. You may either split an expense equally (only with groupid provided), or supply a list of shares. When splitting equally, the authenticated user is assumed to be the payer. When providing a list of shares, each share must include paidshare and owedshare, and must be identified by one of the following: - email, firstname, and lastname - userid Note: 200 OK does not indicate a successful response. The operation was successful only if errors is empty.

    POST /create_expense

  • Write

    Update an expense

    Updates an expense. Parameters are the same as in createexpense, but you only need to include parameters that are changing from the previous values. If any values is supplied for users{index}{property}, all shares for the expense will be overwritten with the provided values. Note: 200 OK does not indicate a successful response. The operation was successful only if errors is empty.

    POST /update_expense/{id}

  • Write

    Restore an expense

    Note: 200 OK does not indicate a successful response. The operation was successful only if success is true.

    POST /undelete_expense/{id}

  • Destructive

    Delete an expense

    Note: 200 OK does not indicate a successful response. The operation was successful only if success is true.

    POST /delete_expense/{id}

Comments

  • Read

    Get expense comments

    GET /get_comments

    GET /get_comments

  • Write

    Create a comment

    POST /create_comment

    POST /create_comment

  • Destructive

    Delete a comment

    Deletes a comment. Returns the deleted comment.

    POST /delete_comment/{id}

Notifications

  • Read

    Get notifications

    Return a list of recent activity on the users account with the most recent items first. content will be suitable for display in HTML and uses only the , , , and tags. The type value indicates what the notification is about. Notification types may be added in the future without warning. Below is an incomplete list of notification types. | Type | Meaning | | ---- | ------- | | 0 | Expense added | | 1 | Expense updated | | 2 | Expense deleted | | 3 | Comment added | | 4 | Added to group | | 5 | Removed from group | | 6 | Group deleted | | 7 | Group settings changed | | 8 | Added as friend | | 9 | Removed as friend | | 10 | News (a URL should be included) | | 11 | Debt simplification | | 12 | Group undeleted | | 13 | Expense undeleted | | 14 | Group currency conversion | | 15 | Friend currency conversion | Note: While all parameters are optional, the server sets arbitrary (but large) limits on the number of notifications returned if you set a very old updatedafter value or limit of 0 for a user with many notifications.

    GET /get_notifications

See How connections work for access and permissions, or browse all integrations.