TrailSplits API terms
Last updated: 2 October 2026
These terms apply when you use the TrailSplits API: the endpoints on api.trailsplits.com, the documented endpoints on trailsplits.com, and the API console. TrailSplits is a small independent project. Questions: support@trailsplits.com.
1. Use
You may use the API in personal, research and commercial projects, including paid apps and websites, within your plan's limits and these terms. One Free account per person or organisation.
2. Keys
Keep your keys secret: use them from your server, not in an app or web page. You are responsible for calls made with your keys until you revoke them in the console.
3. Limits
Calls are rate-limited and counted in credits. Your plan's limits and your usage are shown in the console. Above a limit the API answers 429 with Retry-After. On the Free plan, calls then stop until the next month; nothing is ever charged.
4. Attribution and source licences
- Show “© TrailSplits” and the source credits that come with the data, wherever you show it. On a map, the usual corner credit is enough.
- The data comes from open sources, and their licences apply to you directly. Among them are OpenStreetMap (© OpenStreetMap contributors, ODbL: a database you build from our map data and share falls under its share-alike rules), Copernicus elevation and imagery, national open imagery, and weather from Open-Meteo (CC BY 4.0).
- The full list is at Data sources.
5. Caching
You may cache responses to serve your own users: map tiles as long as their HTTP headers allow, and computed answers (routes, analyses, weather) for up to 30 days.
6. Not allowed
- reselling or redistributing the data as a dataset, mirror or tile service;
- systematically downloading tiles, archives or answers to build a copy;
- using the outputs to train or build a competing geodata service;
- getting around keys, limits or attribution;
- anything illegal.
7. What we keep
We count calls per project and operation. We do not keep the routes, tracks or coordinates you send after we have answered, and our logs leave them out. Your account is handled as described in the Privacy Policy. If you send us your users' locations, you are responsible for being allowed to.
8. Outdoor data can be wrong
- Routes, difficulty grades, closures, snow and weather are information, not a guarantee of safety. Do not present them as one.
- The API is provided as it is, without warranties of accuracy or availability, and without an SLA.
- As far as the law allows, TrailSplits is not liable for any loss arising from using it.
9. Changes
We may change, limit or stop the API, these terms or the plans. We announce material changes on the API pages, normally 30 days ahead. We may suspend a key that is being abused, at once.
API guide · Plans and limits · Terms of Service (your TrailSplits account)