Device roaming
The Device Status SDK allows checking the device roaming status and subscribing to its related events. A device can be in national (different networks in the same country) or international roaming (different networks in another country). Knowing whether the device is connected to a network other than its home one is important for regulatory, security and content delivery reasons.
For example, in some cases for certain transactions to take place, a device needs to be within an area where it is legally allowed to operate or make transactions. Another case would be to ensure a customer's device is exactly where it claims to be to avoid fraud. Other important examples include content or service delivery to avoid extra costs or unexpected roaming charges for accessing them.
Subscribe to Roaming events
The SDK below allows you to subscribe client devices to Device Status roaming events.
import network_as_code as nac
from network_as_code.models.device_status import EventType
# We begin by creating a Network as Code client
client = nac.NetworkAsCodeClient(
token="<your-application-key-here>"
)
# Then, we create an object for the mobile device we want to use
my_device = client.devices.get(
# The phone number does not accept spaces or parentheses
phone_number="+99999991000"
)
# Then we subscribe your device to roaming events.
my_subscription = client.connectivity.subscribe(
event_type=EventType.ROAMING_STATUS,
device=my_device,
# You can tell when the subscription is supposed to expire
subscription_expire_time="2024-04-10T14:13:29Z",
# Use HTTPS to send notifications
notification_url="https://example.com/notify",
notification_auth_token="replace-with-your-auth-token"
)
# Use this to show the roaming subscription status
print(my_subscription)Roaming subscription parameters
| Parameters | Type | Description | Mandatory or Optional |
|---|---|---|---|
event_type | object/string | The status type you want to check. For example EventType.ROAMING_STATUS or org.camaraproject.device-status.v0.roaming-status. | Mandatory |
device | object | The device object previously created for the mobile device we want to use. | Mandatory |
notification_url | string | The recipient's HTTP endpoint, which is a web server configured to receive POST requests. | Mandatory |
notification_auth_token | string | A password used to identify the sender of the notification. | Optional |
subscription_expire_time | object/string | When the subscription should expire. It can be either a date-time object or ISO 8601 formatted date string, for example "2025-08-28T12:40:20.398Z". | Optional |
Roaming event types
| Event type | Type | Description |
|---|---|---|
roaming-status | object/string | EventType.ROAMING_STATUS or org.camaraproject.device-status.v0.roaming-status - Used for receiving updates about when the device switches from roaming ON to roaming OFF and conversely. |
roaming-on | object/string | EventType.ROAMING_ON or org.camaraproject.device-status.v0.roaming-on - Used to receive updates when the device switches from roaming OFF to roaming ON. |
roaming-off | object/string | EventType.ROAMING_OFF or org.camaraproject.device-status.v0.roaming-off - Used to receive updates when the device switches from roaming ON to roaming OFF. |
roaming-change-country | object/string | EventType.ROAMING_CHANGE_COUNTRY or org.camaraproject.device-status.v0.roaming-change-country - Notification is sent when the device in roaming changes country code. |
Simulated device roaming scenarios
The Network as Code simulators have been configured to provide specific device roaming results for specific simulated devices based on their device identifier. This will be helpful in testing your code against the different responses, including possible errors, by simply substituting the device identifier in your code.
The device identifiers and their responses can be found in the following table:
| Device identifier type | Device identifier | HTTP status code | HTTP status code description | Reponse description |
|---|---|---|---|---|
| Phone Number | +99999991000 | 200 | Success | Device is roaming |
| Phone Number | +99999991001 | 200 | Success | Device is not roaming |
| Phone Number | +99999990400 | 400 | Bad Request | |
| Phone Number | +99999990404 | 404 | Not found | |
| Phone Number | +99999990422 | 422 | Unprocessable Content | |
| Phone Number | +99999990500 | 500 | Internal Server Error | |
| Phone Number | +99999990502 | 502 | Bad Gateway | |
| Phone Number | +99999990503 | 503 | Service Unavailable | |
| Phone Number | +99999990504 | 504 | Gateway Timeout |
Getting device roaming status
You can check the device roaming status like so:
print(my_device.get_roaming())Getting device roaming status responses
Getting a devices roaming status will respond with a boolean value indicating whether the device is roaming or not. If the device is roaming, the response will also contain the county code and country name the device is roaming in.
| Response | Type | Description |
|---|---|---|
roaming=True | string | Indicates, that the device is roaming in specified country. For example roaming=True country_code=416 country_name=['JO']. |
roaming=False | string | Indicates, that the device is not roaming. |
Getting roaming notifications
The code snippet below will set up an HTTP server with a POST endpoint. This will allow receiving device roaming status updates. Learn more about the notification URL/auth token and how to create an HTTP server with a POST endpoint for roaming notifications.
Roaming notification handler
# status_handler.py
# run with: uvicorn status_handler:app
from fastapi import FastAPI, Header
from pydantic import BaseModel
from typing_extensions import Annotated
from typing import List, Union
app = FastAPI()
class Device(BaseModel):
phoneNumber: str | None
networkAccessIdentifier: str | None
ipv4Address: str | None
ipv6Address: str | None
class RoamingEventDetail(BaseModel):
device: Device
subscriptionId: str
roaming: bool | None
countryCode: int | None
countryName: List[str] | None
terminationReason: str
class Event(BaseModel):
eventTime: str
eventDetail: RoamingEventDetail
class Data(BaseModel):
device: Device
subscriptionId: str
roaming: RoamingEventDetail
class RoamingStatusNotification(BaseModel):
id: str
source: str
type: str
specversion: str
datacontenttype: str
time: str
eventSubscriptionId: str
event: Event
data: Data
@app.post("/notifications")
def receive_notification(
notification: RoamingStatusNotification,
authorization: Annotated[Union[str, None], Header]
):
if authorization == "Bearer my-token":
# We can now react to the notifications
# based on the Notification object
print(notification)Roaming notification details
This is the notification JSON schema for roaming related notifications.
Remember that the string values represented below are just examples that can be used. So, they should contain your real device-status values.
{
"id": "2628b42e-8789-4fcd-942a-841f16f52897",
"source": "/device-status/v0/subscriptions/90409561-68f5-4360-b12d-9003f4dca8b0",
"type": "org.camaraproject.device-status.v0.roaming-status",
"specversion": "1.0",
"datacontenttype": "application/json",
"time": "2026-04-17T07:31:01.416474Z",
"data": {
"device": {
"phoneNumber": "+99999991000",
"networkAccessIdentifier": "[email protected]",
"ipv4Address": {
"publicAddress": "233.252.0.2",
"privateAddress": "192.0.2.25",
"publicPort": 80
},
"ipv6Address": "2001:db8:1234:5678:9abc:def0:fedc:ba98"
},
"subscriptionId": "90409561-68f5-4360-b12d-9003f4dca8b0",
"roaming": true,
"countryCode": 587
}
}
Roaming event key words
| Roaming-event-detail-keyword values | Type | Description |
|---|---|---|
roaming | boolean/null | True, false or null value indicating wheather the device is roaming or not. |
countryCode | integer/null | Either a contry code indicating which country the device is roaming in or a null value. For example "countryCode":222. |
countryName | string/string array | Either country name(s) indicating which country a device is roaming in or a null value. For example "countryName":["IT"]. |
Shared-keyword values
Check the table below for further information on mandatory, optional values and their types.
The values described here are common to all the Device-Status notification JSON schemas:
| Keyword values | Type | Description |
|---|---|---|
subscriptionId | string | The event subscription identifier. |
source | string | Identifies the source where the event happened. It contains the Network as Code API implementation and subscription ID. |
type | string | The status type being checked and returned by the API. For example roaming-on. |
specversion | string | Representing the specification version. |
datacontenttype | string | Indicates the media type for the event payload encoding. It must be "application/json" in the context of CAMARA APIs |
time | string | The time the event occurred. Date and time are specified in ISO 8601 format, e.g.: "2023-08-20T21:01:02.345Z". |
Device identifiers
| Keyword values | Type | Description | Mandatory or Optional |
|---|---|---|---|
data | object | Object that will contain other objects or strings. Contains multiple device status data, e.g. the subscription id. | Mandatory |
device | object | Object that will contain other objects or strings. Contains multiple device identifiers, e.g. the devices phone number. | Mandatory |
phoneNumber | string | Phone number of the device, with a pattern that matches "^[+]?[0-9]{5,15}$" or a null value. | Optional |
networkAccessIdentifier | string | An email-like external identifier for a device (or subscriber) into the network, with a pattern that matches "^[+]?[0-9]{5,15}$" or a null value. If both the networkAccessIdentifier and phoneNumber are included, phoneNumber will be dropped and networkAccessIdentifier will be retained. | Optional |
ipv4Address | object | Contains an object for IPv4 address values or a null value. It refers to the IPv4 address of the device. An IP address is needed for some flow-oriented services, such as QoD. | Optional |
publicAddress | string | Either the device's public IPv4 address, the Network Address Translation (NAT) behind it or a null value. Learn more about NAT.. | Optional |
privateAddress | string | The device's private IPv4 address if it is behind NAT or a null value. | Optional |
publicPort | integer | The public port used by the device or a null value. A port is necessary, as private address ranges overlap, and public port is used to extend the range for Carrier-grade NAT (CGNAT), a type of large-scale NAT. | Optional |
ipv6Address | integer | Contains the device's IPv6 address or a null value. An IP address is needed for some flow-oriented services, such as QoD. | Optional |
Last updated November 05, 2025