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
I've logged out every variable and everything looks correct, and according to all the documentation I could find this seems to be the correct way to validate a signature. I know I have the correct auth credential exported to my environment as I can send texts no problem. The signature is definitely there and all I got from the docs was to send back the url.toString() and params like so.
According to the security docs Im supposed to be sending back like so
however my requests dont have digits or callers (Is there a messaging centric doc I should be looking at 🤔)? I also noticed a Very subtle callout that these need to be alphabetized?
Then, sort the list of POST variables by the parameter name (using Unix-style case-sensitive sorting order):
What I tried
The code you see above
Setting the url to be my callback url configured in the portal without trailing slash
passing {} for params, alphabetizing params.
If there's a fix or if this is a known issue I'd really appreciate it.
The text was updated successfully, but these errors were encountered:
Hi - Please see details below
The Setup
I'm catching requests from Twilio on a SvelteKit API endpoint. I get the request and all the goodies off of it just fine with the following code
The Problem
I've logged out every variable and everything looks correct, and according to all the documentation I could find this seems to be the correct way to validate a signature. I know I have the correct auth credential exported to my environment as I can send texts no problem. The signature is definitely there and all I got from the docs was to send back the
url.toString()
andparams
like so.According to the security docs Im supposed to be sending back like so
however my requests dont have digits or callers (Is there a messaging centric doc I should be looking at 🤔)? I also noticed a Very subtle callout that these need to be alphabetized?
What I tried
If there's a fix or if this is a known issue I'd really appreciate it.
The text was updated successfully, but these errors were encountered: