Users/report_spam.json returning a 403 error


#1

Calling users/report_spam.json is returning a 403 error.

This started sometime today, reported by multiple users, verified locally.

The response body is text (not JSON) “403 Forbidden: The server understood the request, but is refusing to fulfill it.”

Response headers for the error as as follows
’x-frame-options’ = ‘DENY’
‘x-access-level’ = ‘read-write-directmessages’
‘x-tsa-request-body-time’ = ‘1’
‘Set-Cookie’ = ‘guest_id=; Domain=.twitter.com; Path=/; Expires=Sat, 13-Jan-2018 03:44:36 UTC’
‘Server’ = ‘tsa_a’
‘x-response-time’ = ‘12’
‘Content-Encoding’ = ‘gzip’
‘x-connection-hash’ = ‘5fdde6ce3b3bf543058b2078cd4475f8’
‘x-xss-protection’ = ‘1; mode=block’
‘Cache-Control’ = ‘no-cache’
‘Date’ = ‘Thu, 14 Jan 2016 03:44:36 GMT’
‘Strict-Transport-Security’ = ‘max-age=631138519’
‘Content-Length’ = ‘98’
‘x-content-type-options’ = ‘nosniff’
‘x-transaction’ = ‘af9160ad4f9270e4’
‘Status’ = ‘403 Forbidden’


403 Forbidden for Report User
#2

Thanks for the report - is this consistent / ongoing?

Looking into it.


#3

Yep, just tested it, still happening. Lots of reports from end users too.


#4

I am using the Twitter API to report a user through the following endpoint:
POST users/report_spam

I am submitting the request, along with the necessary parameters but am receiving the following error:
403 Forbidden: The server understood the request, but is refusing to fulfill it.

However, there are no errors.

I know for a fact that the access tokens are valid, as I am using them for a different endpoint. Any help would be greatly appreciated!


#5

Thanks. Checking on this, bear with us please.


#6

One thing that would be a great addition to the report_spam.json end point is allowing users to use the additional reporting options available from the official apps, such as reporting abuse, not just spam.

I’m sure there’s a lot of users out there that would benefit from reporting abuse if they are using other apps or services.


#7

Sorry for delay. Have already raised to attn of eng, and will report back what we hear.


#8

Quick update: eng team said we did a hotfix over the weekend. Given the last update was 5 days ago, can you guys confirm whether or not the issue still persists?

Thanks!


#9

@rchoi Works now…thanks!!


#10

Confirmed that it appears fixed since around the weekend.


#11

Thanks so much for confirming!


#12