We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
com.cognitect.aws/api {:mvn/version "0.8.305"} com.cognitect.aws/endpoints {:mvn/version "1.1.11.568"} com.cognitect.aws/email {:mvn/version "722.2.470.0"} com.cognitect.aws/sns {:mvn/version "718.2.444.0"} com.cognitect.aws/pinpoint {:mvn/version "711.2.411.0"}
I'm attempting to use Pinpoint's phone number validation endpoint, and can't seem to get a proper response.
(ns myapp.aws.pinpoint (:require [cognitect.aws.client.api :as aws])) (def pinpoint (aws/client {:api :pinpoint})) (aws/validate-requests pinpoint true) (defn validate-phone-number [phone] (aws/invoke pinpoint {:op :PhoneNumberValidate :request {:NumberValidateRequest {:PhoneNumber phone :IsoCountryCode "US" }}})) (validate-phone-number "+14085550100")
Response:
{:message "Unsupported Media Type", :cognitect.anomalies/category :cognitect.anomalies/incorrect}
Looking at the request headers, it doesn't appear that the Content-Type header is present, but I'm unsure whether that is truly the root cause:
Content-Type
"x-amz-date" = "20190629T172118Z" "host" = "pinpoint.us-east-1.amazonaws.com" "authorization" = "AWS4-HMAC-SHA256 Credential=...
Amazon's example request appears to include that header.
The text was updated successfully, but these errors were encountered:
Fixed in 5e1a88a.
Sorry, something went wrong.
Fixed in 0.8.335.
No branches or pull requests
Dependencies
Description with failing test case
I'm attempting to use Pinpoint's phone number validation endpoint, and can't seem to get a proper response.
Response:
Looking at the request headers, it doesn't appear that the
Content-Type
header is present, but I'm unsure whether that is truly the root cause:Amazon's example request appears to include that header.
The text was updated successfully, but these errors were encountered: