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 Location Verification v0.2.0 API

The Location Verification v0.2.0 API from Nokia Network as Code — 1 operation(s) for location verification v0.2.0.

Nokia Network as Code Location Verification v0.2.0 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 Location Verification v0.2.0. 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 16 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.

1 operations 1 paths 16 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, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Nokia Network as Code Location Verification v0.2.0 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 1

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

Location Verification v0.2.0 1
POST
/location-verification/v0/verify
Verify the location of a device
verifyLocation-LocV-V0 body → 200400401403404500503

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Device-LocV-V0 (4 properties), ErrorInfo-LocV-V0 (3 properties), VerifyLocationResponse-LocV-V0 (3 properties), VerifyLocationRequest-LocV-V0 (3 properties). Each schema is shown below with its type and property counts.

PhoneNumber-LocV-V0
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…
Device-LocV-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
VerificationResult-LocV-V0
string
Result of a verification request: - TRUE: when the network locates the device within the requested area, - FALSE: when the requested area does not match the ar…
VerifyLocationRequest-LocV-V0
object
3 properties 2 required
Port-LocV-V0
integer
TCP or UDP port number
MatchRate-LocV-V0
integer
Estimation of the match rate between the area in the request (R), and area where the network locates the device (N), calculated as the percent value of the int…
Area-LocV-V0
object
1 property 1 required
MaxAge-LocV-V0
integer
The maximum age (in seconds) of the available location, which is accepted for the verification.
SingleIpv4Addr-LocV-V0
string
A single IPv4 address with no subnet mask
NetworkAccessIdentifier-LocV-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…
DeviceIpv4Addr-LocV-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
AreaType-LocV-V0
string
Type of this area. CIRCLE - The area is defined as a circle.
ErrorInfo-LocV-V0
object
3 properties 3 required
DeviceIpv6Address-LocV-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…
VerifyLocationResponse-LocV-V0
object
3 properties 1 required
LastLocationTime-LocV-V0
string
Timestamp of the last location information. It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allow…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nokia-network-as-code-location-verification-v0-2-0-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.7 API
Nokia Network as Code Device Roaming Status Subscriptions v0.8 API
Nokia Network as Code Device Status v0.5.1 API
Where this information came from

This is an independent, third-party profile of Nokia Network as Code Location Verification v0.2.0 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.