Got a CONFIRMATION Lifecycle event via WebHook {"lifecycle"=>"CONFIRMATION", "executionId"=>"83A0CE64D33F4D6CAFD84030B5111FFF-ER8N", "appId"=>"[FILTERED]", "locale"=>"en", "version"=>"0.1.0", "confirmationData"=>{"appId"=>"[FILTERED]", "confirmationUrl"=>"https://api.smartthings.com/apps/6786c1fe-aa39-4ec7-8339-bcb1eb4e41bc/confirm-registration?token=[FILTERED]&nonce=[FILTERED]"}, "settings"=>{}}
Made a GET request on webhook provided URL
As a result I get 403 response with no body
I cannot understand what is the root cause of the problem, as it was correctly working earlier. Could you provide some help?
Yes, a couple of us noticed this recently and @nayelyz has reported it. I believe it is tied in to an issue the engineering team were already aware of.
I found that persistence could pay off. The only difference I noted between a 403 and a success five minutes later was that different IP addresses were used. As api.smartthings.com was getting handled by a pool of eight IP address it was tempting to think it was a matter of getting lucky with one that was working. I don’t expect it to be anywhere near as simple as that given the sheer scale and complexity of the global AWS platform but it was nice to pretend at the time.
The original thread was the following one. It takes a while to get to the 403 issue.
Thank you for reaching out!
As Graham mentioned, this is already reported and I added your post to that ticket as well for the team’s awareness.
Once we get an update, we’ll share it with you too.
Thank you, @orangebucket@nayelyz! I’ll keep an eye on the thread.
Also, could you tell me approximate timeframes when the issue is expected to be resolved?