#1

Hey!

We are getting an error This client application does not have permission to make write requests. How do we apply for the WRITE access?

The endpoint we are trying to reach is PUT https://ads-api.twitter.com/11/accounts/{accountId}/campaigns/{campaignId}.
Our app id is 9130162.

Thank you!

#3

Jasl692, OKJ hey! Could you please help us here?

#4

Isn’t this just a generic write permission?

Click on the app => settings => then “Edit” near User authentication settings

#5

@Connexinet but isn’t it for user authentication?

Authentication allows users to log in to your App with Twitter. It also allows your App to make specific requests for authenticated users.

So that is for authenticating users via Twitter in our app… Or is it not?

image
image1726×406 36.1 KB

#6

It’s both authentication AND authorization
So if the user did not give “write” permission, you cannot make write operations on their account
Having said that, I am not 100% sure this is applicable to the ads API, but I would say it’s probably 99% the reason for this error
I would try to make this temporary change (note, you will need to authenticate the account with a new access token), and see if that makes a difference

#7

Thank you. Do you know whether that will invalidate all the tokens?
We have multiple user accounts connected to our app. Do you have any idea whether they will all get disconnected?

#8

I have done it in the past and it did not invalidate the tokens.
Having said that, you should not be experimenting on your production app. Do you have a dev/test app? If not, I would create one and test this change on it to see if the error goes a way

#9

Well, there is another app, and it has WRITE access. But the settings that you are talking about are the same as for the app that does not have WRITE access. So it is confusing.

stephinami could you please clarify this?

#10

Oh OK, perhaps your token authorization doesn’t have write access then?
The app level and the token levels can be different (But the app level have to be >= token level).

#11

Hi @SofiaBoSmartly ,

Sorry for missing this. It looks like app 9130162 was only granted for READ access (i.e. Analytics endpoints only). To apply for other Ads API access, you’ll need to submit this here Advertising API License Agreement | Docs | Twitter Developer Platform.

However you may want to apply using another app, because the app 9130162 currently has more than 5 active tokens and we need to apply a restriction of 5 tokens max when giving the Ads API access.

1 Like
#12

Hey @Jasl692 ! Just wanted to let you know that we followed your advice and submitted an application
on Mon Dec 12 for an another app (id: 25917066).

#13

It should be approved now!

#14

Hey!
We are trying to get the elevated access (how it’s described here in Twitter Documentation). We booked a meeting, but no one showed up. We already have 2 client testimonials ready, so what would be the next step?

Thank you!

#15

@Jasl692 Hi! Anything you can do for us here? :blush:

#16

Hi @Dev_Smartlyio,

Could you reach out to your Twitter contact for this? Thank you.

#17

Hi! Update for this one: Our Twitter contact let us know that the elevated access should be approved. We gave it a shot and got the following error:

“APIError: You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated │
│ access via the Developer Portal. You can learn more here: Getting Started with the Twitter API | Docs | Twitter Developer Platform”

App id: 25917066

So unfortunately it didn’t work. Is this something you could prioritize on your end to check what’s missing? Thanks a lot!

#18

Hello, I checked the dev account and the elevated access is still under review status, and not approved. You can let your Twitter contact know to help you double check on the approval.

Related to API access, just to let you know we just announced this https://twitter.com/TwitterDev/status/1621026986784337922 that from 9 Feb free v1.1 and v2 access would no longer be supported.

#19

Amazing thanks for the update @Jasl692 :raised_hands: One major problem here is that we don’t have any official dedicated Twitter contacts any more and basically have been pinging random people on email threads which is not optimal obviously. So appreciate if you can give more context regarding the approval process and if there’s anything we can do to accelerate that.

Thanks for highlighting the announcement regarding access to the Twitter API.

#20

I’ve been told internally that someone reached out to you or someone on your end (previously about the token limit lift), that should be your Twitter contact for now regarding APIs.

I’ll see what I can do to have your elevated access approved, but it’s possible this process may be impacted due to the free API access change I mentioned.

Update:
I’ve checked and unfortunately elevation access requests are on hold till further notice. I’ll let you know if anything changes.