Exclude_reply_user_ids is not working

[mmalbergier]

I’m using
extended_tweet=true
auto_populate_reply_metadata=true
exclude_reply_user_ids=178044546

When replying a tweet that mention two users, and it’s being ignored.
The incoming tweet was 1047204647407157249
And the reply tweet is 1047205162127953920

Don’t know why or don’t understand why both users are being mentioned.

Help would be appreciated

Thanks

[Aurelia]

Hi there - I just tried to reproduce this and I was able to exclude one of two users using the exclude_reply_user_ids parameter. You can see my example with Tweet 1047846687807561729.

The situation you describe does seem strange. Are you able to share the exact series of calls that led you to this situation?

[mmalbergier]

I’m invoking with this parameters.
The tweet I’m answering is 1047921059041857541.
Am I doing something wrong?
This is the answer tweet: https://twitter.com/YznTest2/status/1047921563109142528

----------------------r4nd0m
Content-Disposition: form-data; name=\"status\"

genio genio
----------------------r4nd0m
Content-Disposition: form-data; name=\"in_reply_to_status_id\"

1047921059041857541
----------------------r4nd0m
Content-Disposition: form-data; name=\"auto_populate_reply_metadata\"

true
----------------------r4nd0m
Content-Disposition: form-data; name=\"exclude_reply_user_ids\"

2525054634,178044546
----------------------r4nd0m
Content-Disposition: form-data; name=\"tweet_mode\"

extended

----------------------r4nd0m--

[mmalbergier]

I’ve found that using Multipart parameters as described wont work.
If the same parameters are provided in the QueryString, it works!

[mmalbergier]

I think it should work both kinds of invocations

[Aurelia]

I’m glad you figured it out and, yes, the majority of our Standard APIs only work when parameters are provided in a QueryString.

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.