ATLAS API Support

The Atlas API endpoints need different IDs and parameters. The pages in this section explain what each one is and how to find it.

Things that apply to every Atlas API call

API key. Send your key in the x-api-key header. The api_key query parameter also works, but a key in a URL is easier to leak through logs and browser history. See Get API Key.

curl https://app-api.geposit.se/v2.0/maps/ \
  --header 'x-api-key: {API_KEY}'

Trailing slashes. Some collection URLs only exist with a trailing slash: /v2.0/maps/, /v2.0/layer/, /v2.0/container/, /v2.0/geometry/polygon/ and /v2.0/filter/. Without it the API answers with a redirect (301 or 307), and curl without -L stops there and prints nothing useful. Use the URLs exactly as shown in these Guides.

Placeholders. In the examples, {API_KEY}, {map_id}, {container_id} and so on are placeholders for your own values, and IDs in the example responses such as MAP_ID are made up.

Regions. Calls that take a country use the lower-case code (se, no, dk, fi), and only the countries enabled for your team work. See Region.

IDs

Map ID
Layer ID (a group of areas or points in a map)
Container ID (an area)
Polygon ID (one geography inside an area)
Point ID
Attribute List ID and Attribute List Item ID
Filter ID
Ref ID and Feature ID (the reference data a geography comes from)
Object Types

The quickest way to see most IDs is the web app: see Show Object IDs.