200 OK "not_available" vs 422 SERVICE_NOT_AVAILABLE for not_supported lines

[fernandopradocabrillo]

Hi team,
We would like to have your insights on how you are handling cases where the API is called with a line for which the service is not supported.
Each operator will have its own particular unsupported cases but, for example, for a B2B line, do you return 422 SERVICE_NOT_APPLICABLE or a 200 OK with all fields set to ‘not_available’?

We understand that the 422 is for when the service is not supported at all for an msisdn and the "not_available" is only for cases where the service is available but not for certain properties.

Thanks.

[HuubAppelboom]

@fernandopradocabrillo At KPN we currently return not_available, but are considering to switch to 422 error, that will make the billing a lot easier.

[GillesInnov35]

@fernandopradocabrillo , in France Market kyc-match API has been developed on CAMARA specifications v0.1 which doesn't include any 422 error code.
So, currently a 400 Service not supported (for this phoneNumber) is returned. A 422 SERVICE_NOT_APPLICABLE should be the right one: to be included in the next version.

[ToshiWakayama-KDDI]

Thanks, @fernandopradocabrillo , @HuubAppelboom , @GillesInnov35 ,

Basically we agree with 4xx error to be returned. Same as Orange, our implementation is v0.1, and currently a 404 Not Found is returned. But, for the latest version, we coudl agree that 422 Service Not Applicable should be returned.

Thanks,
Toshi

[fernandopradocabrillo]

Thanks everyone, I think we can close the issue with a common understanding that the proper error should be 422 SERVICE_NOT_AVAILABLE and it will be gradually adopted.