You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional Observation
The endpoint will return 200 OK and the body showing the current state (before the attempted state change) of Shield Mode if using the incorrect body defined in the documentation.
I would expect this to return 400 Bad Request
The text was updated successfully, but these errors were encountered:
Also, to get the endpoint to work, Content-Type header needs to be present (docs mistakenly do Client-Type)
Good catch, didn't notice since I was using my bot lib which already did that. Updating OP and forums post
gmt2001
changed the title
Update Shield Mode Status - Incorrect PUT Body in Documentation
Update Shield Mode Status - Incorrect PUT Body and Headers in Documentation
Dec 3, 2022
Brief description
The PUT body and headers in the documentation for Update Shield Mode Status is incorrect
Incorrect documentation
Expected documentation
Screenshots

Additional Observation
The endpoint will return 200 OK and the body showing the current state (before the attempted state change) of Shield Mode if using the incorrect body defined in the documentation.
I would expect this to return 400 Bad Request
The text was updated successfully, but these errors were encountered: