---
title: "Checks if a POI geofence training is possible with the given parameters"
method: POST
path: "/geofences/v2/trainingTest"
tags: ["Geofences"]
---

# Checks if a POI geofence training is possible with the given parameters

`POST /geofences/v2/trainingTest`

Checks if a POI geofence training is possible with the given request parameters.

The request body contains a training data sample in form of either a device tracking ID 
along with a specific time range for the ingested device telemetry or a WLAN scan.

## Request body

- union
  - object
    - `after` integer, required — Milliseconds elapsed since 1 January 1970 00:00:00 UTC. The value must be within the past 24 hours from the current timestamp
    - `before` integer, required — Milliseconds elapsed since 1 January 1970 00:00:00 UTC. The value must not be greater than current timestamp
    - `id` string, required — This is a unique ID associated with the device data in HERE Tracking. For physical devices the `trackingId` gets assigned to a device when the device is claimed by a user, and for virtual devices it is an external device ID along with the device project `appId`.
  - object
    - `wlan` object[], required — WLAN access points
      - `band` 2.4 | 3.65 | 5 — Frequency range (GHz). Allowed values are 2.4, 3.65, and 5. (Possible future values include 4.9, 5.9, 60, and 900.)
      - `mac` string, required — The MAC address of the WLAN access point. MAC-48 address with colon (:) or hyphen (-) separators, upper or lower case hex digits. Note that if the SSID contains postfix '_nomap', the AP should not be used for positioning. For privacy reasons positioning based on a single WLAN AP is not possible; there has to be at least one other matching wlan or cell.
      - `powrx` integer, required — Received signal level (dBm) at the terminal (Optional)
      - `timestamp` string, date-time — Time of the wlan measurement (UTC) (Optional)

## Response `200`

Returns an object indicating if the training is possible with the given parameters

- object
  - `metadata` object
    - `coordinate` object — Training data position
      - `lat` number, required — Latitude in WGS-84 format, decimal representation ranging from -90 to 90.
      - `lng` number, required — Longitude in WGS-84 format, decimal representation ranging from -180 to 180.
    - `timestamp` integer — Training data timestamp
    - `trackingId` string — This is a unique ID associated with the device data in HERE Tracking. For physical devices the `trackingId` gets assigned to a device when the device is claimed by a user, and for virtual devices it is an external device ID along with the device project `appId`.
    - `usedWlanApCount` number, required — The number of WLAN access point used in training
  - `reason` string
  - `success` boolean, required

## Other responses

- `400` — Bad request The request object is in an incorrect format or has values that are invalid or out of range. If available, further error details are provided in the response body.
- `401` — Unauthorized The request did not provide correct authentication details
- `403` — Forbidden The account does not have the correct privileges
- `404` — Not Found The specified resource was not found
- `422` — Unprocessable Entity The request was well-formed but was unable to be followed due to semantic errors.

---

[API](https://skmtc.net/here/apis/tracking.md) · [All operations](https://skmtc.net/here/apis/tracking/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/here/tracking/versions/efa162f7023c/schema)