search

namaggarwal / splitwise

Python SDK for Splitwise
MIT License
183 stars 46 forks source link

Optional use of API key instead of access tokens #56

Closed rmodi6 closed 3 years ago

rmodi6 commented 3 years ago

Allow the optional use of API keys instead of access tokens as mentioned in the API keys section of Splitwise API Reference:

For speed and ease of prototyping, you can generate a personal API key on your app's details page. You should present this key to the server via the Authorization header as a Bearer token. The API key is an access token for your personal account, so keep it as safe as you would a password. If your key becomes compromised or you want to invalidate your existing key for any other reason, you can do so on the app details page by generating a new key.

namaggarwal commented 3 years ago

This looks good to me. Thank you for your contribution. I will merge this and release a version next week

technillogue commented 3 years ago

oops, i duplicated this in #57

sriramsv commented 3 years ago

@namaggarwal could you please merge this PR: I am trying to build a custom component for splitwise in homeassistant and getting the OAuth callback to work is seeming to be a hard task. If you will merge this, I can resort to using the API_KEY which will be a simpler approach

akompos commented 3 years ago

Ye plus +1 for getting this merged. Just simpler for prototyping

namaggarwal commented 3 years ago

Hello everyone, I apologize for all the delay. My new job is keeping me pretty busy. I promise this will be out this week. I am merging the code, but the release needs some steps to be done

akompos commented 3 years ago

Sounds good! Tell us if there is anything we can help with :)

namaggarwal commented 3 years ago

Thanks. This is now available in version 2.3.0