I have a Python/Django application using python-dwolla 2.2 and I’m confused on constants.access_token. Is the expected workflow to set this with the current user’s token each time I hit the Dwolla API? Or should I always pass the alternate_token kwarg? Neither of these seems like a great solution, so I think maybe I’m missing something.
@jrenaut, I’d recommend passing the token on a per API request basis by using the
alternate_token as shown here. If your app deals with many expiring access tokens that you’re probably storing then this may be the better solution.
Just noting that it’s alternate_token, not alternative_token, for anyone who looks to this for reference.
Whoops, apparently can’t type today. Good catch! Just made the edit