Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
You should definitely add QRcode on page with API keys.
For future use with mobile devices.
Not sure I understand your request here.
Every mobile app currently has the problem that the user has to manually enter or copy+paste the API key. It would be awesome to have the API keys encoded within a QR image so the mobile app can just scan and parse the keys.
Way more convenient to authorize mobile apps etc.
Very interesting suggestion - we will look into this.
We do want to setup oAuth for the API to make this more convenient for developers to build third party integrations but that is a ways off because it will probably be tied into v2 of the API.
This can be a very interesting interim solution, however the only issue is that we do not display the API key after its generated. So you would basically need to regenerate it, get the QR code, and then snapshot it.
You could issue multiple keys/ one key per app without having to implement OAuth.
While OAuth seems to be a good idea for integration in webapps (like twitter or facebook end-user-apps) I think most users want to automate their infrastructure without having a browser.
e.g. it's a PITA to create an OAuth app with twitter/facebook just to get tokens for some command-line tools after they discontinued their old API…
Great point, I think what you mentioned about separate keys + QR code scanning for input will make that easier for mobile apps specifically which was definitely one of the main use cases, it's definitely a conversation for us to have and see what everyone thinks of it.
Great suggestion regardless of the route taken.
You won't be notified about changes to this idea.