PathMates for developers

PathMates is developed in the open. This page lists the PathMates API contract, where the OpenAPI specification lives, and what an integration can and cannot do.

The PathMates API

PathMates runs a Rust (Axum) HTTP API backing a Flutter client, with PostgreSQL via Supabase for storage. The service is hosted at https://pathmates-api.onrender.com. It is the same API the PathMates web app uses; there is no separate public API surface and no rate-limited free tier for third parties.

PathMates OpenAPI specification

The full HTTP contract is generated from the Rust source rather than written by hand, so it does not drift from the implementation. Read it in the repository at backend/openapi.json, or fetch it from the running service:

• https://pathmates-api.onrender.com/api-docs/openapi.json - the OpenAPI document
• https://pathmates-api.onrender.com/swagger-ui - Swagger UI for browsing the same document
• https://pathmates-api.onrender.com/health - service health check

The Flutter client calls the API exclusively through a generated client built from this specification. If you are integrating, generate your own client from the same document rather than hand-writing requests.

Authentication and access

PathMates has no anonymous access, by design. Every endpoint that returns trip content requires an authenticated session belonging to a user with access to that trip, and this includes trips marked public: those are discoverable only to signed-in users, not to the open web. There is no public read API, no API key programme, and no anonymous share link that returns trip data.

In practice this means an automated agent cannot fetch a PathMates itinerary on a user's behalf without that user's credentials. The correct integration pattern is to send the person to sign in and let them act in the app.

Source code and issues

• https://github.com/massimosiani/pathmates - the PathMates source, client and backend
• Architecture notes - stack, patterns, and design decisions
• AI compliance notes - GDPR and EU AI Act positions for the AI features
• Issue tracker - bugs and feature requests

What PathMates does not offer

There is no MCP server, no webhook subscription, no partner or affiliate API, and no booking integration. PathMates holds no travel inventory and processes no reservations, so there is nothing to book against. If any of these would be useful to you, say what you are building at pathmates.travel@gmail.com.

A machine-readable orientation file describing PathMates, when to use it, and where these resources live is published at /llms.txt.