Bad Twitter streaming request: 403 - api

I'm trying to access twitter's api v1.1 filtered streaming endpoint but it gives me 403 error. I don't understand why. I can access other endpoints but not filtered stream for some reason.
It gives me this error-
HTTP ERROR: 403
Problem accessing '/1.1/statuses/filter.json
Reason: Please use V2 filtered and sample volume stream as alternatives

Is this a brand new developer account and app? v1.1 streams are deprecated and new client apps cannot access statuses/filter as of the end of April 2022, in preparation for future removal of the endpoint. The error message directs you to use the replacement v2 filtered stream API instead.

Related

Amazon Connect API didn't response correctly in Postman

I am trying to test Amazon Connect Rest API in Postman. The API name is GetMetricData. In Postman, I have provided all the required information that is mentioned in the documentation. I have provided the JSON body, URL, and Header, although API is responding 200 OK status but in the response, it is throwing the following errors that you can see in the following screenshots.
I have set AWS signature with proper credentials such as access key and secret key
In the second error it is suggesting me to enable Javascript in the browser which is already enabled in my browser.
Can someone please help me here, I don't know where I am doing wrong. As I am totally new in this field, any help would be appreciated.
Thanks
You are submitting the POST request to the UI distribution endpoint for your Amazon Connect instance, not an API endpoint. You are getting HTML and javascript response body back from the UI distribution because this is meant to be consumed by a browser.
Your API request should be sent to a URL that looks like https://connect.us-west-2.amazonaws.com/metrics/historical/<instanceId>. In this example, my Amazon Connect instance is located in the us-west-2 region so I'm using the connect.us-west-2.amazonaws.com endpoint. You can find all available Amazon Connect API endpoints in the documentation here

Apache nifi getTwitter Processor returning 403 forbidden

I want to use Apache Nifi to track real time tweets
i pasted in my keys correctly but all requests return this error :
19:15:20 UTC ERROR
GetTwitter[id=59b5cb18-017e-1000-a6a2-991a653ec138] Received error HTTP_ERROR: HTTP/1.1 403 Forbidden. Will attempt to reconnect
i dont know where the problem is from.
thank you.
403 Forbidden means the Twitter API is rejecting your request - your access keys could be incorrect, or you might not have the right access rights for the endpoint you're accessing.
The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why.
Check that your developer account includes access to the endpoint you’re trying to use. You may also need to get your App allowlisted (e.g. Engagement API or Ads API) or sign up for access.
From https://developer.twitter.com/en/support/twitter-api/error-troubleshooting
Make sure you follow the advice from Twitter here and make note of:
With Essential access, you are only able to make requests to the Twitter API v2 endpoints, and not the v1.1 or enterprise endpoints. You are limited to 500K Tweets/month, and unable to take advantage of certain developer portal functionality such as teams and access to additional App environments
There are limits on what you can do with the Essential access level. See here.
If that doesn't help - please include a screenshot of your GetTwitter config and your version of NiFi.
If it raises 403 error while using GetTwitter processor in nifi.
API Key & consumer key aren't only a problem. Change the Twitter endpoint field while configuring the GetTwitter processor from
Filter Endpoint
to
Firehose Endpoint
In the field of twitter endpoint
Probably this will work!!

Rapid Api- Skyscanner Flight Search gives 403 (Forbidden) error

I was using the free edition of that API for 20 days. There was no problem and status code was 200, I could fetch data . However, suddenly server started to response forbidden.
I have no idea what just happened, I tried to change my api key and nothing has changed. This time, server responses 429, which means 'too many request' with the new api-key. Anyone have an idea what can be the problem is ? I even tried with different accounts , every attempt was a fail for me. My subscription is free edition. Also it says something like this as a response :
Disabled partner with integration ID 27378
Bad news :
Skyscanner decides to stop their API on RapidAPI it won't be available
anymore.
Skyscanner API endpoint is no longer available to RapidAPI service (as confirmed via email from the RapidAPI team).
You can use some other Flight API available on RapidAPI Hub.

"Access Not Configured" error in YouTubeDataAPI

I am integrating one website with youtube channel own. I needed to use the YouTube Data API. Google provides a specific URL to use the GET method in order to get data.
https://www.googleapis.com/youtube/v3/channels?part=snippet&mine=true&key={YOUR_API_KEY} (I used my API here)
When I use it, I got an error with the code 403 and reason accessNotConfigured.
" "message": "Access Not Configured. YouTube Data API has not been used in a project before or it is disabled."
YouTube Data API is enabled in my project. I don't understand where is an error and how can I solve/configure it
Please note that the mine parameter should only be used upon a proper authorization flow.
Also note that a query to the API's Channels endpoint needs to be getting the id of the channel you're interested in.

Api Auto Discovery error in mule logs

Api Auto discovery Error 400... when i deploy my api in cloud(anypoint through runtime manager) it got deployed. but, when i tried to get a response from postman, it says "service not available",i am not able to get a response back from postman.
Is it error 503? In that case the explanation is that the API is not correctly paired to the API in API Manager with client credentials and Autodiscovery. See https://support.mulesoft.com/s/article/API-returns-503-Service-Unavailable-error-to-clients