Features Endpoints
Create, read, update, and delete map features (data points) via the API.
Features Endpoints
All feature endpoints operate on a specific map and require authentication:
/api/v1/maps/{map_id}/features
Read features
GET /api/v1/maps/{map_id}/features
Returns features as a GeoJSON FeatureCollection.
Response:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "uuid",
"geometry": {
"type": "Point",
"coordinates": [-3.7038, 40.4168]
},
"properties": {
"label": "Madrid Office",
"address": "Gran Via 1",
"category": "office"
}
}
]
}
Query parameters:
- Filters can be applied via query parameters matching your filter configuration
- Pagination parameters for large datasets
- Spatial queries using viewport bounds
Create features
POST /api/v1/maps/{map_id}/features
Add new features to the map. Send a GeoJSON FeatureCollection.
Request body:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"type": "Point",
"coordinates": [2.1734, 41.3851]
},
"properties": {
"label": "Barcelona Office",
"address": "Passeig de Gracia 100",
"category": "office"
}
}
]
}
Notes:
- Properties should use field slugs as keys
- Geometry supports Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon
- Coordinates use [longitude, latitude] order (GeoJSON standard)
Update features
PUT /api/v1/maps/{map_id}/features
Update existing features. Features are matched by ID.
Upsert by remote ID
If your map has a remoteField configured, you can use it to upsert features:
- Features with a matching remote ID value get updated
- Features without a match get created
- This is ideal for syncing with external databases
Delete features
DELETE /api/v1/maps/{map_id}/features
Delete features from the map. Specify feature IDs in the request body.
Bulk operations
PATCH /api/v1/maps/{map_id}/features
Perform bulk create, update, or delete operations in a single request.
Import limits
- Free plan: 100 features via API
- Pro/Enterprise: unlimited
Geometry types
Features support standard GeoJSON geometry types:
Point: single location (marker)LineString: a line/pathPolygon: a closed areaMultiPoint,MultiLineString,MultiPolygon: collections of the above
Coordinates always use [longitude, latitude] order per the GeoJSON specification (not lat/lng).