Nokia Network as Code Location Verification v1.0.0 API

openapi: 3.2.0
info:
  title: Nokia Network As Code Location Verification v1.0.0 API
  version: 1.0.0
  termsOfService: https://developer.networkascode.nokia.io/legal/terms-of-service
  x-refined-note:
  - x-badges differs across the merged source definitions and was not carried
  - x-camara-commonalities differs across the merged source definitions and was not carried
  - x-category differs across the merged source definitions and was not carried
  - x-collections differs across the merged source definitions and was not carried
  - x-long-description differs across the merged source definitions and was not carried
  - x-public differs across the merged source definitions and was not carried
  - x-thumbnail differs across the merged source definitions and was not carried
  - x-version-lifecycle differs across the merged source definitions and was not carried
  - x-website differs across the merged source definitions and was not carried
  description: 'Operations tagged Location Verification v1.0.0 across 2 of this provider''s published API definitions: nokia-network-as-code-camara-openapi.yml, nokia-network-as-code-platform-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: '{apiRoot}/geofencing-subscriptions/v0.3'
  variables:
    apiRoot:
      default: http://localhost:9091
      description: API root
- url: '{apiRoot}/geofencing-subscriptions/v0.4'
  variables:
    apiRoot:
      default: http://localhost:9091
      description: API root
- url: https://network-as-code.p-eu.rapidapi.com
tags:
- name: Location Verification v1.0.0
paths:
  /location-verification/v1/verify:
    post:
      tags:
      - Location Verification v1.0.0
      summary: Verify the location of a device
      description: 'Verify whether the location of a device is within a requested area. The operation returns a verification result and, optionally, a match rate estimation for the location verification in percent.

        '
      operationId: verifyLocation
      parameters:
      - $ref: '#/components/parameters/x-correlator-LocV-V1'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/VerifyLocationRequest-LocV-V1'
            examples:
              DEVICE_INSIDE_AREA_FALSE_PHONE_NUMBER:
                value:
                  device:
                    phoneNumber: '+99999991000'
                  area:
                    areaType: CIRCLE
                    center:
                      latitude: 50.735851
                      longitude: 7.10066
                    radius: 50000
              DEVICE_INSIDE_AREA_TRUE_PHONE_NUMBER:
                value:
                  device:
                    phoneNumber: '+99999991001'
                  area:
                    areaType: CIRCLE
                    center:
                      latitude: 50.735851
                      longitude: 7.10066
                    radius: 50000
      responses:
        '200':
          description: Location verification result
          headers:
            x-correlator:
              $ref: '#/components/headers/x-correlator-LocV-V1'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/VerifyLocationResponse-LocV-V1'
              examples:
                VERIFICATION_TRUE:
                  summary: Match
                  description: The network locates the device within the requested area
                  value:
                    verificationResult: 'TRUE'
                    lastLocationTime: '2023-09-07T10:40:52.000Z'
                VERIFICATION_FALSE:
                  summary: No match
                  description: The requested area does not match the area where the network locates the device
                  value:
                    verificationResult: 'FALSE'
                    lastLocationTime: '2023-09-07T10:40:52.000Z'
                VERIFICATION_UNKNOWN:
                  summary: Unknown
                  description: The network cannot locate the device
                  value:
                    verificationResult: UNKNOWN
                VERIFICATION_PARTIAL:
                  summary: Partial match
                  description: The requested area partially matches the area where the network locates the device
                  value:
                    verificationResult: PARTIAL
                    matchRate: 74
                    lastLocationTime: '2023-09-07T10:40:52.000Z'
        '400':
          $ref: '#/components/responses/Generic400-LocV-V1'
        '401':
          $ref: '#/components/responses/Generic401-LocV-V1'
        '403':
          $ref: '#/components/responses/Generic403-LocV-V1'
        '404':
          $ref: '#/components/responses/Generic404-LocV-V1'
        '422':
          $ref: '#/components/responses/VerifyLocationUnprocessableEntity422-LocV-V1'
        '429':
          $ref: '#/components/responses/Generic429-LocV-V1'
        '500':
          $ref: '#/components/responses/Generic500-LocV-V1'
        '503':
          $ref: '#/components/responses/Generic503-LocV-V1'
      security:
      - openId:
        - location-verification:verify
    servers:
    - url: '{apiRoot}/geofencing-subscriptions/v0.3'
      variables:
        apiRoot:
          default: http://localhost:9091
          description: API root
    - url: '{apiRoot}/geofencing-subscriptions/v0.4'
      variables:
        apiRoot:
          default: http://localhost:9091
          description: API root
components:
  schemas:
    DeviceIpv4Addr-LocV-V1:
      type: object
      description: '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 (observed) IP addresses in use by the device (this information can be obtained by various means, for example from some DNS servers).


        If the allocated and observed IP addresses are the same (i.e. NAT is not in use) then  the same address should be specified for both publicAddress and privateAddress.


        If NAT64 is in use, the device should be identified by its publicAddress and publicPort, or separately by its allocated IPv6 address (field ipv6Address of the Device object)


        In all cases, publicAddress must be specified, along with at least one of either privateAddress or publicPort, dependent upon which is known. In general, mobile devices cannot be identified by their public IPv4 address alone.

        '
      properties:
        publicAddress:
          $ref: '#/components/schemas/SingleIpv4Addr-LocV-V1'
        privateAddress:
          $ref: '#/components/schemas/SingleIpv4Addr-LocV-V1'
        publicPort:
          $ref: '#/components/schemas/Port-LocV-V1'
      anyOf:
      - required:
        - publicAddress
        - privateAddress
      - required:
        - publicAddress
        - publicPort
      example:
        publicAddress: 84.125.93.10
        publicPort: 59765
    ErrorInfo-LocV-V1:
      description: Common schema for errors
      type: object
      required:
      - status
      - code
      - message
      properties:
        status:
          type: integer
          description: HTTP status code returned along with this error response
        code:
          type: string
          description: Code given to this error
        message:
          type: string
          description: Detailed error description
    DeviceIpv6Address-LocV-V1:
      description: '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 the /64 prefix).

        '
      type: string
      format: ipv6
      example: 2001:db8:85a3:8d3:1319:8a2e:370:7344
    Port-LocV-V1:
      description: TCP or UDP port number
      type: integer
      minimum: 0
      maximum: 65535
    Area-LocV-V1:
      description: Base schema for all areas
      type: object
      properties:
        areaType:
          $ref: '#/components/schemas/AreaType-LocV-V1'
      required:
      - areaType
      discriminator:
        propertyName: areaType
        mapping:
          CIRCLE: '#/components/schemas/Circle'
    VerifyLocationResponse-LocV-V1:
      description: Response to a location verification request
      type: object
      required:
      - verificationResult
      properties:
        lastLocationTime:
          $ref: '#/components/schemas/LastLocationTime-LocV-V1'
        verificationResult:
          $ref: '#/components/schemas/VerificationResult-LocV-V1'
        matchRate:
          $ref: '#/components/schemas/MatchRate-LocV-V1'
    AreaType-LocV-V1:
      type: string
      description: 'Type of this area.

        CIRCLE - The area is defined as a circle.

        '
      enum:
      - CIRCLE
    VerifyLocationRequest-LocV-V1:
      description: Request to verify the location of a device. Device is not required when using a 3-legged access token, following the rules in the description.
      type: object
      properties:
        device:
          $ref: '#/components/schemas/Device-LocV-V1'
        area:
          $ref: '#/components/schemas/Area-LocV-V1'
        maxAge:
          $ref: '#/components/schemas/MaxAge-LocV-V1'
      required:
      - area
    MaxAge-LocV-V1:
      description: The maximum age (in seconds) for the location known by the implementation, which is accepted for the verification. Absence of maxAge means "any age" and maxAge=0 means a fresh calculation.
      type: integer
      example: 120
    NetworkAccessIdentifier-LocV-V1:
      description: A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Local Identifier}@{Domain Identifier}). Unlike the telephone number, the network access identifier is not subjected to portability ruling in force, and is individually managed by each operator.
      type: string
      example: 123456789@domain.com
    SingleIpv4Addr-LocV-V1:
      description: A single IPv4 address with no subnet mask
      type: string
      format: ipv4
      example: 84.125.93.10
    Device-LocV-V1:
      description: '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 the below specified device identifiers:


        * `ipv4Address`

        * `ipv6Address`

        * `phoneNumber`

        * `networkAccessIdentifier`


        NOTE1: the MNO might support only a subset of these options. The API invoker can provide multiple identifiers to be compatible across different MNOs. In this case the identifiers MUST belong to the same device

        NOTE2: for the Commonalities release v0.4, we are enforcing that the networkAccessIdentifier is only part of the schema for future-proofing, and CAMARA does not currently allow its use. After the CAMARA meta-release work is concluded and the relevant issues are resolved, its use will need to be explicitly documented in the guidelines.

        '
      type: object
      properties:
        phoneNumber:
          $ref: '#/components/schemas/PhoneNumber-LocV-V1'
        networkAccessIdentifier:
          $ref: '#/components/schemas/NetworkAccessIdentifier-LocV-V1'
        ipv4Address:
          $ref: '#/components/schemas/DeviceIpv4Addr-LocV-V1'
        ipv6Address:
          $ref: '#/components/schemas/DeviceIpv6Address-LocV-V1'
      minProperties: 1
    MatchRate-LocV-V1:
      description: 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 intersection of both areas divided by the network area, that is (R ∩ N) / N * 100. Included only if VerificationResult is PARTIAL.
      type: integer
      minimum: 1
      maximum: 99
    LastLocationTime-LocV-V1:
      description: 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 allows 2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
      example: '2023-09-07T10:40:52Z'
      format: date-time
      type: string
    VerificationResult-LocV-V1:
      description: "Result of a verification request:\n  - `TRUE`: when the network locates the device within the requested area,\n  - `FALSE`: when the requested area does not match the area where the network locates the device,\n  - `UNKNOWN`: when the network cannot locate the device,\n  - `PARTIAL`: when the requested area partially match the area where the network locates the device. A `match_rate` is included in the response.\n"
      type: string
      enum:
      - 'TRUE'
      - 'FALSE'
      - UNKNOWN
      - PARTIAL
    PhoneNumber-LocV-V1:
      description: A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with '+'.
      type: string
      pattern: ^\+[1-9][0-9]{4,14}$
      example: '+123456789'
  responses:
    VerifyLocationUnprocessableEntity422-LocV-V1:
      description: Unprocessable Entity
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            LOCATION_VERIFICATION_422_UNABLE_TO_FULFILL_MAX_AGE:
              summary: Unable to fulfill maxAge
              description: The system is not able to provide the fresh location required by the client
              value:
                status: 422
                code: LOCATION_VERIFICATION.UNABLE_TO_FULFILL_MAX_AGE
                message: Unable to provide expected freshness for location
            GENERIC_422_UNPROCESSABLE_ENTITY:
              summary: Unprocessable entity
              description: The request was well-formed but was unable to be processed due to semantic errors or not applicable values. This is the generic error code for 422 responses.
              value:
                status: 422
                code: UNPROCESSABLE_ENTITY
                message: 'Value not acceptable: ...'
            GENERIC_422_DEVICE_NOT_APPLICABLE:
              summary: Service not applicable to the device
              description: The provided device is not compatible with the requested operation, according to the service provider rules.
              value:
                status: 422
                code: DEVICE_NOT_APPLICABLE
                message: The device is not applicable for the requested operation
            GENERIC_422_DEVICE_IDENTIFIERS_MISMATCH:
              summary: Device identifiers mismatch
              description: Several device identifiers are provided but do not match the same device
              value:
                status: 422
                code: DEVICE_IDENTIFIERS_MISMATCH
                message: The provided device identifiers do not match the same device
            GENERIC_422_UNSUPPORTED_DEVICE_IDENTIFIERS:
              summary: None of the provided device identifiers is supported by the implementation
              description: Message may list the supported device identifiers
              value:
                status: 422
                code: UNSUPPORTED_DEVICE_IDENTIFIERS
                message: 'Supported device supported are: ...'
            GENERIC_422_UNIDENTIFIABLE_DEVICE:
              summary: No identifier provided
              description: No device identifier provided for the device to be located
              value:
                status: 422
                code: UNIDENTIFIABLE_DEVICE
                message: A device must be provided
    Generic400-LocV-V1:
      description: Bad Request
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_400_INVALID_ARGUMENT:
              summary: Generic Invalid Argument
              description: Invalid Argument. Generic Syntax Exception
              value:
                status: 400
                code: INVALID_ARGUMENT
                message: Client specified an invalid argument, request body or query param.
            GENERIC_400_OUT_OF_RANGE:
              summary: Generic Out of Range
              description: Out of Range. Specific Syntax Exception used when a given field has a pre-defined range or a invalid filter criteria combination is requested
              value:
                status: 400
                code: OUT_OF_RANGE
                message: Client specified an invalid range.
    Generic503-LocV-V1:
      description: Service unavailable
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_503_UNAVAILABLE:
              summary: Generic Unavailable
              description: Service is not available. Temporary situation usually related to maintenance process in the server side
              value:
                status: 503
                code: UNAVAILABLE
                message: Service unavailable
    Generic404-LocV-V1:
      description: Not found
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_404_NOT_FOUND:
              summary: Generic Not Found
              description: Resource is not found
              value:
                status: 404
                code: NOT_FOUND
                message: '{{resource}} is not found'
            GENERIC_404_DEVICE_NOT_FOUND:
              summary: Some identifier cannot be matched to a device
              description: One or more of the provided device identifiers do not match any device
              value:
                status: 404
                code: DEVICE_NOT_FOUND
                message: No device found for a provided identifier
    Generic429-LocV-V1:
      description: Too Many Requests
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_429_QUOTA_EXCEEDED:
              description: Request is rejected due to exceeding a business quota limit
              value:
                status: 429
                code: QUOTA_EXCEEDED
                message: Either out of resource quota or reaching rate limiting.
            GENERIC_429_TOO_MANY_REQUESTS:
              description: API Server request limit is overpassed
              value:
                status: 429
                code: TOO_MANY_REQUESTS
                message: Either out of resource quota or reaching rate limiting.
    Generic401-LocV-V1:
      description: Unauthorized
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_401_UNAUTHENTICATED:
              summary: Generic Unauthenticated
              description: Request cannot be authenticated
              value:
                status: 401
                code: UNAUTHENTICATED
                message: Request not authenticated due to missing, invalid, or expired credentials.
            GENERIC_401_AUTHENTICATION_REQUIRED:
              summary: Generic Authentication Required
              description: New authentication is needed, authentication is no longer valid
              value:
                status: 401
                code: AUTHENTICATION_REQUIRED
                message: New authentication is required.
    Generic403-LocV-V1:
      description: Forbidden
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_403_PERMISSION_DENIED:
              summary: Generic Permission Denied
              description: Permission denied. OAuth2 token access does not have the required scope or when the user fails operational security
              value:
                status: 403
                code: PERMISSION_DENIED
                message: Client does not have sufficient permissions to perform this action.
            GENERIC_403_INVALID_TOKEN_CONTEXT:
              summary: Invalid access token context
              description: Reflects some inconsistency between information in some field of the API and the related OAuth2 Token
              value:
                status: 403
                code: INVALID_TOKEN_CONTEXT
                message: '{{field}} is not consistent with access token.'
    Generic500-LocV-V1:
      description: Internal server error
      headers:
        x-correlator:
          $ref: '#/components/headers/x-correlator-LocV-V1'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorInfo-LocV-V1'
          examples:
            GENERIC_500_INTERNAL:
              summary: Generic Internal
              description: Problem in Server side. Regular Server Exception
              value:
                status: 500
                code: INTERNAL
                message: Internal server error
  headers:
    x-correlator-LocV-V1:
      description: Correlation id for the different services
      schema:
        type: string
  parameters:
    x-correlator-LocV-V1:
      name: x-correlator
      in: header
      description: Correlation id for the different services
      schema:
        type: string
    x-rapidapi-host:
      name: x-rapidapi-host
      in: header
      required: true
      description: The API's Host value as defined in the RapidAPI Hub.
      schema:
        type: string
        example: network-as-code.p-eu.rapidapi.com
  securitySchemes:
    openId:
      description: OpenID Connect authentication
      type: openIdConnect
      openIdConnectUrl: https://example.com/.well-known/openid-configuration
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-rapidapi-key
      description: Your RapidAPI key
externalDocs:
  description: Project documentation at Camara
  url: https://github.com/camaraproject/DeviceLocation
x-refined-from:
- nokia-network-as-code-camara-openapi.yml
- nokia-network-as-code-platform-openapi.json