Ads api v4 audience API endpoint returns 403

[MySocialData]

Hi,

We’re trying to add users to a newly created created tailored audience using the new audience API announced last week ( https://developer.twitter.com/en/docs/ads/audiences/api-reference/audience) but the reply is invariably 403 Forbidden.

send: b’POST /4/accounts/<account_id>/tailored_audiences/<audience_id>/users HTTP/1.1\r\nHost: ads-api.twitter.com\r\nuser-agent: twitter-ads version: 3.0.0 platform: Python 3.6 (CPython/linux)\r\nAccept-Encoding: gzip, deflate\r\nAccept: /\r\nConnection: keep-alive\r\nContent-Type: application/json\r\nContent-Length: 0\r\nAuthorization: OAuth oauth_nonce=“154121593665093205981536049212”, oauth_timestamp=“1536049212”, oauth_version=“1.0”, oauth_signature_method=“HMAC-SHA1”, oauth_consumer_key="", oauth_token="", oauth_signature=""\r\n\r\n’

reply: ‘HTTP/1.1 403 Forbidden\r\n’
header: content-disposition header: content-encoding header: content-length header: content-type header: date header: server header: set-cookie header: set-cookie header: strict-transport-security header: x-connection-hash header: x-content-type-options header: x-frame-options header: x-response-time header: x-transaction header: x-xss-protection {‘errors’: [{‘code’: 87, ‘message’: ‘Client is not permitted to perform this action.’}]}

Here’s a sample payload:

[{“operation_type”: “Update”, “params”: {“effective_at”: “2018-09-04T08:37:44.418548+00:00”, “expires_at”: “2019-09-04T08:37:44.418604+00:00”, “users”: [{“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}, {“twitter_id”: [""]}]}}]

Any help will be appreciated.

Kind regards,

My Social Database

[MySocialData]

FTR: I had included <key>, <sig>, <hashid> in relevant places but didn’t check the preview. key, token, secret and twitter-ids were all present. The twitter ids are hashed (hashlib.sha256(x).hexdigest()).

BTW, the sample code in the documentation uses unhashed everything so we also tried that: same result.

[imit8me]

Thanks for raising the issue! The reason for the error is due to the fact that you’ll need to be whitelisted for access to the new Audience API. Please reach out to your Twitter representative and they should be able to help you get setup.

Thanks!