Problem description
Communalities guided to use "common public" language in the API. Phone number instead of MSISDN was an example used there.
The API payload follows this guideline uses "phoneNumber", however documentation for this payload sometimes does not. This can cause some confusions (actually already did).
Example:
There are 2 issues here:
1) confusion for a reader: If the API creates request for a MSISDN, why the attribute is called phoneNumber and if it is the same?
2) documentation is a place where it is especially important to use a developer friendly language (and above this is exact opposite)
Expected action
Use phone number everywhere. Only use MSISDN/IMSI in the explanation what is considered as a SimSwap only.
Problem description Communalities guided to use "common public" language in the API. Phone number instead of MSISDN was an example used there. The API payload follows this guideline uses "phoneNumber", however documentation for this payload sometimes does not. This can cause some confusions (actually already did). Example:
There are 2 issues here: 1) confusion for a reader: If the API creates request for a MSISDN, why the attribute is called phoneNumber and if it is the same? 2) documentation is a place where it is especially important to use a developer friendly language (and above this is exact opposite)
Expected action Use phone number everywhere. Only use MSISDN/IMSI in the explanation what is considered as a SimSwap only.
Additional context