This endpoint facilitates the creation of polygons within a container.
Custom polygons, defined by users and not attached to administrative boundaries, require the 'the_geom' field, which is a stringified GeoJSON representation of the polygon.
The GeoJSON object type must be 'MultiPolygon'. Default polygons, system-defined and linked to administrative boundaries, need to be added with 'ref_id', 'feature_id', 'geo_type', and 'geo_name' or 'geo_code'
In instances of ambiguous geographic names (e.g., multiple areas named 'Holm'), using 'geo_code' instead of 'geo_name' resolves the ambiguity. When ambiguity persists, the API returns an error message containing possible codes for the name.
For postcodes, 'geo_code' and 'geo_name' hold the same value.
A 'geo_name' or 'geo_code' that matches no reference data returns 422, not 500 — the geo is unknown to us, the request itself was well formed.