Issues with invalid of unsupported phone number from the API

Hi there @Chops ,

Welcome to the Community.

That is bizarre indeed. If both API calls are the same minus the phone number, there shouldn’t be a reason for one call to work vs the other. I will reach out to colleagues and see if there is anything to report on this.

Best,

Alex

Thanks for the answer, we’ll probably have to wire up Twillo verification on phone inputs now.  Bit of a side-step for us in terms of our use case but it seems like there is no other option.  It should be noted in your docs though, saying E.164 compliant isn’t the whole picture.  It’s E.164 + a valid phone number.  It’s an extra cost to us so would be nice to know ahead of development.

Thanks.

I’m having the same issue with a valid phone number using the 2022-10-17 API endpoint.

Data in question

{
    'phone_number': '+1330219####'
}

Error response

{
    'id': '851832d9-38b1-403c-9833-d8e27def81df', 
    'status': 400, 
    'code': 'invalid', 
    'title': 'Invalid input.', 
    'detail': 'Invalid or unsupported phone number', 
    'source': {
        'pointer': '/data/attributes/phone_number'
    }, 
    'meta': {}
}

Hi,
I’m having the same issue with valid phone numbers checked on https://www.phonevalidator.com/

this is the error I got:

{"errors":[{"id":"ec3024fd-da00-490f-8c79-62eb7e0b6df3","status":400,"code":"invalid","title":"Invalid input.","detail":"Invalid or unsupported phone number","source":{"pointer":"/data/attributes/phone_number"},"meta":{}}]}

Can you please investigate if it’s something on Klavyo side? We tried several real phone number with or without phone prefix and no one was working.

Thanks