FastGIS
FastGIS is the platform: a spatial analysis and routing backend, and the API that three clients are built on.
| What it is | Where it runs | |
|---|---|---|
| Web app | GRASS Runner — run GRASS modules on server-side data and explore the results on a 3D globe | Any browser, at the site root |
| Epona | The rider app — navigation, turn-by-turn, roadbooks, capture, offline maps, CarPlay and Android Auto | iOS and Android |
| EpicRide | The desktop client — route planner, discovery, track editor, roadbook and StoryMap authoring | epicride.fastgis.eu |
One API serves all three: 374 paths across 435 operations, documented in full for developer subscribers.
Where to start
If you use the product, go to Product. The web app section covers GRASS Runner tool by tool; Epona covers the rider app, including group ride, push-to-talk voice and live calls.
If you are integrating, go to Developers. The API reference is generated from the running server's OpenAPI schema, so it cannot drift from what is actually deployed. It is available to developer subscribers; the tutorials are open to everyone.
If you run the servers, the Operations documentation — architecture,
deployment, configuration and data-pipeline runbooks — is published separately at
/guide-ops/ and requires you to be signed in.
Authenticating
Three mechanisms coexist, and every operation in the reference states which one it uses:
| Scheme | Credential | Used by |
|---|---|---|
| API key | X-API-Key header | The JSON API, Epona, EpicRide |
| Session cookie | fastgis_session, set by signing in | The server-rendered web pages |
| Public token | The token in the link | Expiring share links such as /live/view/{token} |
Generate an API key from your profile page, then:
curl -H "X-API-Key: $FASTGIS_KEY" https://api.fastgis.eu/grass/env
:::tip Two failure modes, not one Omitting the header entirely returns 422 — FastAPI reports it as a missing required field. Sending a key that is unknown or revoked returns 401. If you are debugging a client, that distinction tells you which half of the problem you have. :::
What is covered here
This site is being rebuilt. The Product pages currently document the web app and the rider app; the desktop client, the shared-riding features, the data products (MTB trails, beaches, friluftsliv POI, TET), accounts and tiers, and the story tools are shipped but not yet written up. Pages that still carry a "last revised" banner have not been re-checked against the running system.
The API reference is complete — it is generated, not written.