Create new fence, assign to multiple projects
Decommission notice
Purpose
This endpoint creates a new fence and assigns it to multiple projects.
Request data
HTTPS method: POST
- Constants and parameters enclosed in curly brackets { } must be replaced with their values.
- Please see the following Request parameters section with the required and optional parameters tables for their values. The generic request format is as follows.
URL request format
https://{baseURL}/geofencing/{versionNumber}/fences/fence?key={Your_API_Key}&adminKey={Your_Admin_Key}curl command request format
curl -v -XPOST -H "Content-type: application/json" -d '{ "name": "fence_name", "type": "Feature", "projects": ["project_1_id", ...], "geometry": { "radius": radius_in_meters, "type": "Point", "shapeType": "shape_type", "coordinates": [longitude, latitude] }, "properties": { //Optional "key": "value" }}' https://{baseURL}/geofencing/{versionNumber}/fences/fence?key={Your_API_Key}&adminKey={Your_Admin_Key}'POST request body
{ "name": "fence_name", "type": "Feature", "projects": ["project_1_id", ...], "geometry": { "radius": radius_in_meters, "type": "Point", "shapeType": "shape_type", "coordinates": ["longitude", "latitude"] }, "properties": "key": "value" }}Request parameters
The following table describes the parameters that can be used in a request.
- Required parameters must be used or the call will fail.
- Optional parameters may be used.
- The order of request parameters is not important.
Required parameters | Description |
|---|---|
| The base URL for calling the API. |
| Service version number. |
| An API Key valid for the requested service. |
| A valid Admin Key. |
Optional parameters | Description |
|---|---|
| If set to |
Response data
Response body
{ "name": "fence_name", "id": "fence_id", "type": "Feature", "projects": [project_1_id, ... , project_N_id], "geometry": { "radius": radius_in_meters, "type": "Point", "shapeType": "shape_type", "coordinates": [longitude, latitude] }, "properties": { "key:" "value" }}Response fields
The following data tables describe all of the fields that can appear in a response. Fields are listed by the response section they belong to and in the order that they appear in the response.
Primary fields | |
|---|---|
Field | Description |
| The name of the fence. |
| The UUID of the fence. |
| In the current version its always “Feature”. |
| The list of projects the fence was assigned to. |
| An object that describes fence geometry. See the Custom fence shapes section. |
| (Optional) An object containing user-defined properties of the fence. Its content varies between fences. |
projects array | |
Field | Description |
| The UUID of a project. |
| The name of a project. |
Response codes
Code | Meaning & possible causes |
|---|---|
| Created |
| Bad request:
|
| Forbidden:
|
Example
Create a new fence and assign it to multiple projects.
URL request example
https://api.tomtom.com/geofencing/1/fences/fence?key={Your_API_Key}&adminKey={Your_Admin_Key}POST request body example
{ "name": "No-fly zone 23", "type": "Feature", "projects": [ "131db271-752e-4462-bd7a-ac948864110e", "36188f87-03ea-4fd4-b606-68d28f781365" ], "geometry": { "radius": 75, "type": "Point", "shapeType": "Circle", "coordinates": [-67.137343, 45.137451] }, "properties": { "maxSpeedKmh": 70 }}Response body example
{ "name": "No-fly zone 23", "id": "aaab6d78-1738-45bd-a78b-ff3a7ba839f3", "type": "Feature", "projects": [ "131db271-752e-4462-bd7a-ac948864110e", "36188f87-03ea-4fd4-b606-68d28f781365" ], "geometry": { "radius": 75, "type": "Point", "shapeType": "Circle", "coordinates": [-67.137343, 45.137451] }, "properties": { "maxSpeedKmh": 70 }}