Skip to content

change consumer_key to api_key in readme #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
change consumer key to api key in project readme
  • Loading branch information
KellyKiiru committed Aug 13, 2023
commit 82941b313a31bf2a37852f0982def72f3400a1f1
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,11 @@ Individual API features have folders where you can find examples of usage in sev

In order to run the samples in this repository you will need to set up some environment variables. You can find your credentials and bearer token in the App inside of your Project in the [dashboard of the developer portal](https://developer.twitter.com/en/portal/projects-and-apps).

For OAuth 1.0a samples, you will need to export your consumer key and secret in your terminal. Be sure to replace `<your_consumer_key>` and `<your_consumer_secret>` with your own credentials without the `< >`.
For OAuth 1.0a samples, you will need to export your consumer key and secret in your terminal. Be sure to replace `<your_api_key>` and `<your_api_key_secret>` with your own credentials without the `< >`.

```bash
export CONSUMER_KEY='<your_consumer_key>'
export CONSUMER_SECRET='<your_consumer_secret>'
export API_KEY='<your_api_key>'
export API_KEY_SECRET='<your_api_key_secret>'
```

For samples which use bearer token authentication, you will need to export the bearer token. Be sure to replace `<your_bearer_token>` with your own bearer token without the `< >`.
Expand Down