Better clarity around naming of API keys
There is an inconsistency in how API keys are described.
On https://developer.twitter.com/en/apps/123456 - I see:
Consumer API keys
abc123 (API key)
qwertyuiiopkjhgfds (API secret key)
However, the Python3 and Ruby documentation say:
consumerkey = '' # Add your consumer key here
consumersecret = '' # Add your consumer secret here
Is an API key the same as a consumer key? If so, why have they been given different names?
On https://developer.twitter.com/en/docs/basics/authentication/guides/bearer-tokens - it tells me to use 'API key:API secret key'
We have fixed this by correcting the wording and adding a screenshot for further clarity: https://developer.twitter.com/en/docs/labs/tweets-and-users/quick-starts/get-users
Thanks Terence, this is great feedback, so great that we corrected the wording following your suggestion, and added a screenshot for further clarity.
This is very useful. We started a process of aligning on a single set of terms a couple of years ago but as this report shows, we can do much better. Thank you for this feedback!