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 Reachability Status Retrieve v1 API

The Device Reachability Status Retrieve v1 API from Nokia Network as Code — 1 operation(s) for device reachability status retrieve v1.

Nokia Network as Code Device Reachability Status Retrieve v1 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 Reachability Status Retrieve v1. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 1 operation across 1 path, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: {apiRoot}/geofencing-subscriptions/v0.3, {apiRoot}/geofencing-subscriptions/v0.4.

1 operations 1 paths 12 schemas 1 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
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Nokia Network as Code Device Reachability Status Retrieve v1 API declares 1 security scheme for authenticating requests. It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration. By default, every request must be authenticated.

  • openId — OpenID Connect authentication

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Device Reachability Status Retrieve v1 1
POST
/device-status/device-reachability-status/v1/retrieve
Get the current reachability status information
getReachabilityStatus 1 param body → 200400401403404422429503

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Device-DS-RE-V1 (4 properties), ErrorInfo-DS-RE-V1 (3 properties), ReachabilityStatusResponse-DS-RE-V1 (3 properties), DeviceIpv4Addr-DS-RE-V1 (3 properties). Each schema is shown below with its type and property counts.

ConnectivityType-DS-RE-V1
string
DATA: The device is connected to the network for Data usage (regardless of the SMS reachability) SMS: The device is connected to the network only for SMS usage
RequestReachabilityStatus-DS-RE-V1
object
The request to retrieve the current roaming-status for the requested device.
1 property
DeviceIpv4Addr-DS-RE-V1
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
Port-DS-RE-V1
integer
TCP or UDP port number
PhoneNumber-DS-RE-V1
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…
Device-DS-RE-V1
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
LastStatusTime-DS-RE-V1
string
Last time that the associated device reachability status was updated
NetworkAccessIdentifier-DS-RE-V1
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…
ReachabilityStatusResponse-DS-RE-V1
object
3 properties 1 required
ErrorInfo-DS-RE-V1
object
The error object used for error-cases.
3 properties 3 required
DeviceIpv6Address-DS-RE-V1
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…
SingleIpv4Addr-DS-RE-V1
string
A single IPv4 address with no subnet mask

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nokia-network-as-code-device-reachability-status-retrieve-v1-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 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.7 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 Reachability Status Retrieve v1 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.