Getting error 403 and 453

21_hagen · 2024-11-09T02:42:16.530Z

Hey so I am just starting to ease into the integration world where I am trying to get 2 platforms to integrate with each other everything seems to look right except for these two errors and I was wondering if anyone knew what the issue is. From what I have seen people have said that it is because of lack of permissions but i do not know how I could request higher permissions. If someone could help me out I would greatly appreciate any help.

MarkusKauppinen · 2024-11-09T14:47:34.055Z

Understanding the error 453 You currently have access to a subset of Twitter API v2 endpoints Announcements

As announced previously, we have deprecated our legacy Twitter API access tiers. By default, developers have access to the Free tier of the Twitter API. This access level gives access to: V1.1 Media Endpoints to upload media V1.1 OAuth endpoints (Login with Twitter) V2 Manage Tweet endpoints to create/post Tweets V2 users/me endpoint If you call other v1.1 Twitter API endpoint, you will get the following response: { "errors": [ { "message": "You currently have acc…

Things have changed just a little after the annoucement above:

Upcoming updates to the Self Serve X API Announcements

Since our initial launch a year ago, the Self Serve X API has been used by developers to support a wide range of use-cases. We are constantly working on improving our API offerings for developers and will be making the following changes: Free tier Developers on the Free tier will be able to Post 500 Posts per month using the X API. Additionally, you can read 100 Posts per month to test out the API. Note: We will continue enabling verified services who post weather alerts, transport updates an…

So, we have four access tiers to choose from: Free, Basic, Pro and Enterprise access.

You may receive a 403 or 453 if trying to call an API endpoint that’s not available in your access tier.

And we should use the V2 API for almost everything as v1.1 API is mostly deprecated now.