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
You can send X-Audit-Log-Reason along with creating a guild scheduled event and with updating a guild scheduled event. This, of course, is not documented. (deleting a guild scheduled event seems to not take this header into account)
Steps to Reproduce
send the X-Audit-Log-Reason header when making a request
it shows up in audit log
Expected Behavior
Documented behavior happens: most routes that take audit log headers are documented so it is expected that routes this is not documented for do not have audit logs -- this one does though.
Current Behavior
Undocumented behavior happens. (wow I've never heard of DIscord having undocumented behavior this is a first)
Screenshots/Videos
Client and System Information
I'm on a custom library using Python, and Canary 107833 on Linux. (should this field be removed lol? The template is called "API Bug Report" what does it have to do with client system??)
The text was updated successfully, but these errors were encountered:
Description
You can send
X-Audit-Log-Reason
along with creating a guild scheduled event and with updating a guild scheduled event. This, of course, is not documented. (deleting a guild scheduled event seems to not take this header into account)Steps to Reproduce
X-Audit-Log-Reason
header when making a requestExpected Behavior
Documented behavior happens: most routes that take audit log headers are documented so it is expected that routes this is not documented for do not have audit logs -- this one does though.
Current Behavior
Undocumented behavior happens. (wow I've never heard of DIscord having undocumented behavior this is a first)
Screenshots/Videos
Client and System Information
I'm on a custom library using Python, and Canary 107833 on Linux. (should this field be removed lol? The template is called "API Bug Report" what does it have to do with client system??)
The text was updated successfully, but these errors were encountered: