twitterdev / postman-twitter-api

Postman Collection for the Twitter API v2

This is a Postman Collection for the Twitter API v2 endpoints.

Refer to the main Twitter API documentation for more details.

If you have an API-related question, you can also discuss in the developer community forum.

Installation

Quick install

Go to the Collection and click Run in Postman.

Manual install

You can also download this Collection from a GitHub repo here: https://github.com/twitterdev/postman-twitter-api

Environment

This Collection includes a pre-configured Environment. You will need to set up the following variables in order to run each request (depending on the authentication type used by the request you are sending):

Name	Description
consumer_key	Your consumer key
consumer_secret	Your consumer secret
access_token	Your access token
token_secret	Your access token secret
bearer_token	Your bearer token

postman-twitter-api's Issues

চচ

Get followers work around

          `https://api.twitter.com/2/users/me?user.fields=public_metrics`

Thats the solution to get total followers count and following count.

Originally posted by @MuhammedQuresh in xdevplatform/Twitter-API-v2-sample-code#130 (comment)

. N

V2 Route GET /2/users/by/username/:username/following

In the twitter website the route GET /2/users/by/username/:username/following has been added to the Basic Access product

but after trying hitting it it does not seem to exist. Also, it does not exist here in Postman.

Is this route legit?

API v2 > Authenticated User Lookup

Postman Authenticated User Lookup URL has to be

https://api.twitter.com/2/users/me

instead of

https://api.twitter.com/2/me

Don't know if PR in Postman was delivered.

z

Connect

          Development 

Originally posted by @MahdiAl-Qubli in #14 (comment)

Collection at https://t.co/twitter-api-postman lost all the variable substitutions in auth

The collection at https://t.co/twitter-api-postman (full link: https://www.postman.com/twitter/workspace/twitter-s-public-workspace/collection/9956214-784efcda-ed4c-4491-a4c0-a26470a67400?ctx=documentation) lost all the variable substitutions in various settings, mainly auth.

For example, it is supposed to have a top level auth of

	"auth": {
		"type": "bearer",
		"bearer": [
			{
				"key": "token",
				"value": "{{bearer_token}}",
				"type": "string"
			}
		]
	},

And it does in the source code.

But the version in that Workplace just have empty string:

You can also see this if you export the collection from there:

Expected behavior

The collection there should be as the same as the source code, so others can simply fork or export and use it.

Actual behavior

It is not. All the variable substitutions are lost.