I’m trying to make use of certain API endpoints like this one, but I’m having trouble getting a User Access Token.
In previous versions of the API, this could all be done on a local machine via API calls. It seems like the only way to get a User Access Token now is to have a publicly accessible
redirect_uri that uses the HTTPS protocol. Is this correct?
If so, this severely inhibits my development process and forces me to pay for a web server just to go through basic development.
What you’re trying to do is still possible - it is based on the environment you are in:
In addition to the ideas above you can use a reverse tunneling system to provide SSL
A quick start method for this is NGROK https://ngrok.com/ personally I use my live Server and Reverse SSH my local system to it so my live server handles SSL termination.
Then my development environment is more similar to live so testing and development is more realistic to the expected/live environment. For any cookie/session problems.
So basically the workaround is to register and use
localhost as the
That only works if your dev environment is at
http://localhost in order to capture the token.
Manually jiggerpokey of the token handling logic not withstanding
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.