rubyaustralia / melbourne-ruby

Organisers notes and processes
54 stars 5 forks source link

Automating your finances (and the Up API) #160

Closed ptagell closed 4 years ago

ptagell commented 4 years ago

A totally unsolicited bucket of tips relating specifically to managing money automatically.

ptagell commented 4 years ago

@colquhounking - if I were to take > 5 but < 10 mins would that work? Can get < 5 if I'm brutal and speak faster.

ceels commented 4 years ago

Between 5 and 10 will be fine!

ptagell commented 4 years ago

Some notes from my talk:

Why we built the Up API: https://up.com.au/blog/api_lets_hack_on_banking/ API Docs: https://developer.up.com.au/ Invite code: https://hook.up.me/paul

davich commented 4 years ago

Really enjoyed the talk, Thanks!. I had a couple more questions if you don't mind. For the security focused consumer, do you have things like

Thanks

mtcmorris commented 4 years ago

@davich - awesome ideas - cheers!

Cycling API keys is straight forward - you only ever have one access token - generating a new token will effectively revoke the old one.

For 2FA I don't quite follow - do you mean as a part of token generation? Or as part of accessing the API?

davich commented 4 years ago

As part of accessing the API As a client I'm about to GET the balance on my account. before I make that get call, I call generate_2fa_token on the API. The API makes an outbound call to my url (that I've pre-configured) with the 2fa token. I then use that token in my GET request. And that token is valid for the next 30 minutes (or whatever). Same concept as how some sites SMS a code to the mobile number they have on file for you. But this would be a POST request to the url they have on file. This could stop someone getting access to your account if your API key leaked.

VanessaNimmo commented 4 years ago

Video is finally up - apologies for the delay! https://youtu.be/AQVw0i-5tRc