To get started with the Splitwise API, you'll need to:
The Splitwise API is under constant development, and while we do try to keep it fairly stable, the output formats change fairly quickly.
If these examples don't clarify an issue you're having, send us an email at firstname.lastname@example.org and we'll get back to you ASAP.
All API requests should be signed with an OAuth token (i.e. consumer token, request token, or access token)
HTTP error codes are returned in the following situations:
Nested parameters (e.g. users[first_name]) are currently broken server-side. To indicate a nested parameter, use a DOUBLE underscore (e.g. users__1__first_name).
Boolean parameters should be indicated with a value of 0 or 1.
For a step-by-step blog post about connecting to Splitwise with OAuth in Ruby, see this blog post for a more detailed walkthrough.
NOTE: Authorization API calls do not require OAuth access tokens (but do require OAuth consumer or request tokens), since they’re how you fetch an access token in the first place. All other API calls do require OAuth access tokens in the HTTP_AUTHORIZATION header.