Building on FastGIS

FastGIS is a commercial platform. The application, the API and the clients are not open source, and the API documentation is available to developer subscribers.

If you have developer access, the full reference lives at fastgis.eu/guide-dev. Sign in with your account to read it.

Access is granted per group: an administrator adds you to a group carrying the docs:api capability, and you inherit it from the membership. An account on its own is not enough — being a rider does not make you an integrator — and if you open the reference without it, the page you land on tells you exactly which capability is missing and how to ask for it.

:::tip Not a subscriber yet? Get in touch and tell us what you want to build. We would rather have that conversation than guess. :::

What is behind it

API reference	Every one of the 374 paths and 435 operations, generated directly from the running server's OpenAPI schema — so it cannot drift from what is actually deployed
Realtime protocol	The /live WebSocket contract: frame types in both directions, close codes, reconnect semantics. Not expressible in OpenAPI, so it is written by hand
Offline packs	The tile and pack formats, and the freshness manifest a client polls to decide what to download
OGC services	Features, Processes and Maps, with working QGIS and ogr2ogr recipes

Authentication is by X-API-Key, with a session cookie accepted on the routes a browser needs and public tokens on expiring share links. Keys are generated from your profile page.

What you can read without a subscription

Plenty, and it is not a teaser:

• The whole Product section — what the rider app, the desktop client and the data products actually do.
• The tutorials, which walk through real analyses in the web app.
• Every dataset's licence and attribution, which is published openly on purpose. If you are deciding whether you can build on our data, you should not have to buy something to find out. GET /mtb/sources and GET /friluft/sources answer without a key.

A note on the source

You will not find a public repository. The platform is closed source, and the documentation reflects that: there are no links to a repository you cannot open, and no "edit this page" button pointing at one.

What we do publish is the behaviour — endpoints, formats, protocols and limits — because an integrator needs those to build, and a licence needs those to be honest.