How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nokia Network as Code Device Roaming Status Subscriptions v0.7 API

The Device Roaming Status Subscriptions v0.7 API from Nokia Network as Code — 2 operation(s) for device roaming status subscriptions v0.7.

Nokia Network as Code Device Roaming Status Subscriptions v0.7 API is one of 31 APIs that Nokia Network as Code publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Device Roaming Status Subscriptions v0.7. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 4 operations across 2 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: {apiRoot}/geofencing-subscriptions/v0.3, {apiRoot}/geofencing-subscriptions/v0.4, https://network-as-code.p-eu.rapidapi.com.

4 operations 2 paths 21 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://network-as-code.p-eu.rapidapi.com
Authentication
OpenID Connect, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Nokia Network as Code Device Roaming Status Subscriptions v0.7 API declares 2 security schemes for authenticating requests. It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration. An API key is passed in the header as x-rapidapi-key (ApiKeyAuth).

  • openId — OpenID Connect authentication
  • ApiKeyAuth — Your RapidAPI key

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Device Roaming Status Subscriptions v0.7 4
POST
/device-status/device-roaming-status-subscriptions/v0.7/subscriptions
Create a device roaming status event subscription for a device
createDeviceRoamingStatusSubscription 1 param body → 201202400401403409422429
GET
/device-status/device-roaming-status-subscriptions/v0.7/subscriptions
Retrieve a list of device roaming status event subscription
retrieveDeviceRoamingStatusSubscriptionList 1 param → 200400401403
GET
/device-status/device-roaming-status-subscriptions/v0.7/subscriptions/{subscriptionId}
Retrieve a roaming status event subscription for a device
retrieveDeviceRoamingStatusSubscription 2 params → 200400401403404
DELETE
/device-status/device-roaming-status-subscriptions/v0.7/subscriptions/{subscriptionId}
Delete a device-roaming-status event subscription for a device
deleteDeviceRoamingStatusSubscription 2 params → 202204400401403404

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Subscription-DS-ROS-V0 (8 properties), CloudEvent-DS-ROS-V0 (7 properties), SubscriptionRequest-DS-ROS-V0 (5 properties), Config-DS-ROS-V0 (4 properties). Each schema is shown below with its type and property counts.

CloudEvent-DS-ROS-V0
object
The notification callback
7 properties 5 required
PhoneNumber-DS-ROS-V0
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…
DeviceIpv6Address-DS-ROS-V0
string
The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to…
CreateSubscriptionDetail-DS-ROS-V0
object
The detail of the requested event subscription.
1 property
ErrorInfo-DS-ROS-V0
object
3 properties 3 required
SingleIpv4Addr-DS-ROS-V0
string
A single IPv4 address with no subnet mask
DeviceIpv4Addr-DS-ROS-V0
object
The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (o…
3 properties
SinkCredential-DS-ROS-V0
object
A sink credential provides authentication or authorization information necessary to enable delivery of events to a target.
1 property 1 required
Source-DS-ROS-V0
string
Identifies the context in which an event happened - be a non-empty URI-reference like: - URI with a DNS authority: https://github.com/cloudevents mailto:cncf-w…
NetworkAccessIdentifier-DS-ROS-V0
string
A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Loc…
Device-DS-ROS-V0
object
End-user equipment able to connect to a mobile network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide t…
4 properties
EventTypeNotification-DS-ROS-V0
string
roaming-status - Event triggered when the device switch from roaming ON to roaming OFF and conversely roaming-on - Event triggered when the device switch from…
SubscriptionAsync-DS-ROS-V0
object
Response for a device reachability status operation managed asynchronously (Creation or Deletion)
1 property
Subscription-DS-ROS-V0
object
Represents a event-type subscription.
8 properties 5 required
DateTime-DS-ROS-V0
string
Timestamp of when the occurrence happened. Must adhere to RFC 3339.
Config-DS-ROS-V0
object
Implementation-specific configuration parameters needed by the subscription manager for acquiring events. In CAMARA we have predefined attributes like subscrip…
4 properties 1 required
SubscriptionEventType-DS-ROS-V0
string
roaming-status - Event triggered when the device switch from roaming ON to roaming OFF and conversely roaming-on - Event triggered when the device switch from…
Port-DS-ROS-V0
integer
TCP or UDP port number
Protocol-DS-ROS-V0
string
Identifier of a delivery protocol. Only HTTP is allowed for now
SubscriptionId-DS-ROS-V0
string
The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this conce…
SubscriptionRequest-DS-ROS-V0
object
The request for creating a event-type event subscription
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nokia-network-as-code-device-roaming-status-subscriptions-v0-7-api-openapi.yml Raw ↑

Other APIs Nokia Network as Code publishes across the network.

Nokia Network as Code Call Forwarding Signal v0.3.0 API
Nokia Network as Code Congestion Insights v1.0.0 API
Nokia Network as Code Consent Info v0.1.0 API
Nokia Network as Code Device Reachability Status Retrieve v1.1.0 API
Nokia Network as Code Device Reachability Status Retrieve v1 API
Nokia Network as Code Device Reachability Status Subscriptions v0.7 API
Nokia Network as Code Device Reachability Status Subscriptions v0.8 API
Nokia Network as Code Device Roaming Status Retrieve v1.1.0 API
Nokia Network as Code Device Roaming Status Retrieve v1 API
Nokia Network as Code Device Roaming Status Subscriptions v0.8 API
Nokia Network as Code Device Status v0.5.1 API
Nokia Network as Code Device Swap v1.0.0 API
Where this information came from

This is an independent, third-party profile of Nokia Network as Code Device Roaming Status Subscriptions v0.7 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.