Developer API
The TourPro developer API lets your own scripts and integrations read your data. Access works through personal access tokens: each token acts as you and can only see the tours you can see.
Phase 1 is read-only: you can fetch your identity, your tours, and schedule events.
Create a token
Open your profile
In the web app, open your Profile and choose the Developer tab.
Create the token
Click Create token, give it a name (for example, the script or service that will use it), and confirm.
Copy it now
TourPro shows the token once. Copy it and store it like a password. If you lose it, revoke the token and create a new one.
Call the API
Send the token as a bearer credential:
Authorization: Bearer tourpro_...| Endpoint | Returns |
|---|---|
GET /api/v1/me | Your user id, name, and email |
GET /api/v1/tours | The tours you can access |
GET /api/v1/tours/:tourId/events | Schedule events for a tour, filtered by your permissions and visibility |
Base URL is the API host (for example https://api.tourpro.app), not the web app.
curl https://api.tourpro.app/api/v1/tours \
-H "Authorization: Bearer tourpro_..."The API is rate limited to 120 requests per minute per token. Past the limit you get a 429 response with RateLimit headers describing the window.
Revoke a token
Back on the Developer tab, click Revoke next to a token and confirm. Revocation is immediate and permanent: create a fresh token if you need a replacement.
What a token can see
A token never sees more than you do:
- Tours: only tours you created or belong to.
- Events: only events visible to your role and venue dates on that tour, and only when you have schedule-view permission.
- Everything is read-only. Nothing in the API can change your data.
Session sign-ins from the app do not work on the API. /api/v1/* accepts tourpro_ tokens only, so a stolen browser session cannot be replayed against it.