Bad Authentication data In Twitter Search API

[ankit061990]

curl -X POST “https://api.twitter.com/1.1/tweets/search/fullarchive/dev.json” -d ‘{“query”:“string”,“maxResults”:“100”,“fromDate”:“201805030000”, “toDate”:“201806010000”}’ -H “Authorization:Bearer TOKEN”

Bearer TOKEN = Consumer Key : Consumer Secret.

So am i right for Bearer Token?? and if i wrong then suggest me to generate the Bearer token.

when i run this script on console then {“error”:{“message”:“Bad Authentication data.”,“sent”:“2018-06-06T06:45:59+00:00”,“transactionId”:“0045b7d6009317eb”}} OR 401 status code is coming. So please suggest me for the solution.

[KvdohertyQU]

Hi @ankit061990,

You can authenticate using either a Bearer Token or your Consumer Key and Secret. You can read more about that process here: https://developer.twitter.com/en/docs/tweets/search/api-reference/premium-search.html#Authentication 1.

An example of what a curl request would look like with a Bearer Token is below:

curl --request POST
–url https://api.twitter.com/1.1/tweets/search/fullarchive/InsertEnvNameHere.json
–header 'authorization: Bearer InsertBearerTokenHere
–header ‘content-type: application/json’
–data ‘{
“query”: “Pizza and Chips”,
“tag”: “TestTag”,
“fromDate”: “201804150000”,
“toDate”: “201805130000”,
“maxResults”: 100
}’

Best,
Kevin