From 7ad9199ef8da2a604b3b73a19f326d91b3d6a2a9 Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Mon, 12 Aug 2024 15:38:50 +0100 Subject: [PATCH 1/2] Update CAMARA Mobile Device Identifier API.yaml --- code/API_definitions/CAMARA Mobile Device Identifier API.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/CAMARA Mobile Device Identifier API.yaml b/code/API_definitions/CAMARA Mobile Device Identifier API.yaml index 9160b9f..c10f958 100644 --- a/code/API_definitions/CAMARA Mobile Device Identifier API.yaml +++ b/code/API_definitions/CAMARA Mobile Device Identifier API.yaml @@ -50,7 +50,7 @@ info: - IPv6 address - IPv4 address - In scenarios where a primary MSISDN is shared between multiple devices, each of which has its own "secondary" MSISDN (e.g. OneNumber), the MSISDN passed by the API consumer will be treated as the secondary MSISDN, and hence the identifier returned will be that of the relevant associated device (such as a smartwatch). In such scenarios, the "primary" device (e.g. smartphone) is usually allocated the same primary and secondary MSISDN, and hence providing the primary MSISDN will always return the identity of the primary device and not any associated devices. + In scenarios where a main phone number is shared between multiple devices, each of which has its own individual "secondary" phone number (e.g. connectivity plans that let you share your airtime and data allowances with a smartwatch or eSIM-enabled tablet), the phone number passed by the API consumer will be treated as the secondary phone number, and hence the identifier returned will be that of a single device associated with that phone number (e.g. smartphone, smartwatch, or eSIM-enabled tablet). In such scenarios, the "primary" device (usually the smartphone) is normally allocated the same main and secondary phone numbers, and hence providing the main phone number will always return the identity of the primary device and not any associated devices. ### Authorization and authentication From ad3a9a11aa447ea3edf820345fa4fff15d4437a5 Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Mon, 12 Aug 2024 15:45:21 +0100 Subject: [PATCH 2/2] Update CAMARA Mobile Device Identifier API.yaml --- code/API_definitions/CAMARA Mobile Device Identifier API.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/CAMARA Mobile Device Identifier API.yaml b/code/API_definitions/CAMARA Mobile Device Identifier API.yaml index c10f958..7b75003 100644 --- a/code/API_definitions/CAMARA Mobile Device Identifier API.yaml +++ b/code/API_definitions/CAMARA Mobile Device Identifier API.yaml @@ -50,7 +50,7 @@ info: - IPv6 address - IPv4 address - In scenarios where a main phone number is shared between multiple devices, each of which has its own individual "secondary" phone number (e.g. connectivity plans that let you share your airtime and data allowances with a smartwatch or eSIM-enabled tablet), the phone number passed by the API consumer will be treated as the secondary phone number, and hence the identifier returned will be that of a single device associated with that phone number (e.g. smartphone, smartwatch, or eSIM-enabled tablet). In such scenarios, the "primary" device (usually the smartphone) is normally allocated the same main and secondary phone numbers, and hence providing the main phone number will always return the identity of the primary device and not any associated devices. + In scenarios where a main phone number is shared between multiple devices, each of which has its own individual "secondary" phone number (e.g. connectivity plans that let you share your airtime and data allowances with a smartwatch or eSIM-enabled tablet), the phone number passed by the API consumer will be treated as the secondary phone number, and hence the identifier returned will be that of the single device associated with that phone number (e.g. smartphone, smartwatch, or eSIM-enabled tablet). In such scenarios, the "primary" device is usually allocated the same main and secondary phone numbers, and hence providing the main phone number to the API will return the identity of the primary device (usually the smartphone) and not any associated devices. ### Authorization and authentication