Alay Posted September 28, 2019 Share Posted September 28, 2019 Hey, I'm having an issue exercising the PUT RSVP functionality of the REST API. For some reason the Key isn't picked up on PUT requests. It works fine for POST, DELETE, and GET requests. Any ideas what the issue might be? See below POSTMAN screenshot. Link to comment Share on other sites More sharing options...
Alay Posted September 28, 2019 Author Share Posted September 28, 2019 I stepped around the issue by editing events.php and duplicating the PUT method to a POST method... workaround for now but not the best 🙂 Link to comment Share on other sites More sharing options...
bfarber Posted September 28, 2019 Share Posted September 28, 2019 Is there some reason you are sending the key as a query string parameter instead of in an HTTP header, as recommended? Link to comment Share on other sites More sharing options...
Alay Posted September 28, 2019 Author Share Posted September 28, 2019 3 minutes ago, bfarber said: Is there some reason you are sending the key as a query string parameter instead of in an HTTP header, as recommended? Postman simplicity. It's secured to a particular IP. I swapped it to a header and had the same issue still though. Haven't tested it via OAuth yet. Link to comment Share on other sites More sharing options...
bfarber Posted September 30, 2019 Share Posted September 30, 2019 I suppose feel free to submit a ticket - the only way that exception code (2S290/6) would show up is if no access token and no API key were detected in the request. Perhaps for some reason your server isn't passing through all of the request data for a PUT method request or something along those lines, but we'd need to take a look at your site to determine that. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.