Phone number validation - use phone type validation rules for SKY API

We are receiving an error when adding a constituent to Raiser's Edge, when including certain phone numbers:
"Error: ContactBusinessLogicPhoneNumberIsInvalid (code 50013). The phone number XXXXXXXXX is invalid".


We don't have any validation set on the phone types being used for this so we were stumped as to why we would get an error. After chatting to the support team, I was told that this is because there is some (seemingly undocumented) validation happening:
"All operations that write phone numbers use the configured base country for each tenant (Database view > Configuration > General > Country). If a requested phone number does not contain an international code, we assume the phone number is for the base country and validate it as such. If a phone number fails validation for the base country, we have no way of guessing which country code should be applied to the number. The operation fails to avoid writing invalid phone numbers to the database."


This doesn’t seem like best practice. In Raiser's Edge, you can set formatting rules on each phone type. What is the point of being able to set format restrictions at the Phone Type level, if the API is just ignoring those and applying some blanket rule? If the system allows you to set your own validation patterns on each phone type and these are enforced in other parts of the system, then the API should also follow these rules.


Our phone types are not set up to have any validation on them, and that is a business decision we have made, understanding the risks and potentially incorrect data involved. We shouldn’t be forced to undergo an additional level of validation that is actually preventing those constituents from being added to the database altogether (due to this happening in the “Add constituent“ process).


Is there potential scope to implement a change to phone number validation within the SKY API so that it uses the rules set up at the phone type level?