The first time I was just watching, determined not to press the button, but when I received the response, I was startled into pressing it.
The second time, I just stepped back from my keyboard, and my cat came flying out of the back room and walked on the keyboard, triggering the request.
The third time, I was holding my cat, and a train rumbled by outside, rattling my desk and apparently triggering the switch to send the request.
The fourth time, I checked the tracks, was holding my cat, and stepped back from my keyboard. Next thing I heard was a POP from my ceiling, and the request was triggered. There was a small hole burned through my keyboard when I examined it. Best I can figure, what was left of a meteorite managed to hit at exactly the right time.
I'm not going to try for a fifth time.
It's a bit like Jeopardy, really.
A sort of quantum commenting conundrum, I guess.
For a brief moment I thought this was some quantum-magical side effect you were describing and not some API error.
If you auth with the bearer token "And There Are No Friends At Dusk." then the API will call you and tell you which request you wanted to send.
Ah. Newbie mistake. You need to turn OFF your computer and disconnect from the network BEFORE sending the request. Without this step you will always receive a response before the request is issued.