- name
- ubtrippin
- version
- 2.0.0
- description
- Manages travel for your user via UBTRIPPIN — trips, items, loyalty programs, family, city guides, events, concerts, notifications, and more. Use when the user asks about their trips, upcoming travel, flights, hotels, train bookings, concert tickets, event tickets, loyalty numbers, family travel, or wants to manage their travel tracker. Requires a UBTRIPPIN API key from ubtrippin.xyz/settings.
UBTRIPPIN Skill
UBTRIPPIN is a personal travel tracker that parses booking confirmation emails and organises them into trips. It also handles event tickets — concerts, theater, sports, festivals — from providers like Ticketmaster, AXS, Eventbrite, and more. As an agent, you can read and manage a user's trips, items (flights, hotels, trains, tickets/events, etc.), loyalty vault, family groups, city guides, and more via REST API.
Setup (First Time)
- Ask your user to visit ubtrippin.xyz/settings and generate an API key.
- The key looks like:
ubt_k1_<40 hex chars>. Store it securely. - Ask for their registered sender email — the email address they use to forward bookings (typically their personal inbox). This is their "allowed sender" in UBTRIPPIN.
- You'll need both to operate: the API key for reads/writes, the email address for adding new bookings via forwarding.
- After setup, call
GET /api/v1/me/profileand offer to set the user's home airport, currency preference, and seat preference viaPATCH /api/v1/me/profile.
Authentication
All API calls use a Bearer token:
Authorization: Bearer ubt_k1_<your_key>Base URL: https://www.ubtrippin.xyz
Rate limit: 100 requests/minute per API key. HTTP 429 if exceeded — back off 60 seconds.
API Endpoints
Trips
List All Trips
GET /api/v1/tripsQuery params: ?status=upcoming (optional filter)
Response:
{
"data": [
{
"id": "uuid",
"title": "Tokyo Spring 2026",
"start_date": "2026-04-01",
"end_date": "2026-04-14",
"primary_location": "Tokyo, Japan",
"travelers": ["Ian Rogers"],
"notes": null,
"cover_image_url": "https://...",
"share_enabled": false,
"created_at": "2026-02-15T10:00:00Z",
"updated_at": "2026-02-15T10:00:00Z"
}
],
"meta": { "count": 1 }
}Ordered by start_date descending (soonest upcoming / most recent first).
Get Trip with All Items
GET /api/v1/trips/:idResponse includes full trip object with nested items array. Each item has: id, trip_id, kind, provider, traveler_names, start_ts, end_ts, start_date, end_date, start_location, end_location, summary, details_json, status, confidence, needs_review, timestamps.
Item kinds: flight, hotel, train, car, ferry, activity, ticket, other
Create Trip
POST /api/v1/trips
Content-Type: application/json
{ "title": "Summer in Provence", "start_date": "2026-07-01", "end_date": "2026-07-14" }Update Trip
PATCH /api/v1/trips/:id
Content-Type: application/json
{ "title": "Updated Title", "notes": "Remember sunscreen" }Delete Trip
DELETE /api/v1/trips/:idRename Trip
POST /api/v1/trips/:id/rename
Content-Type: application/json
{ "title": "New Trip Name" }Merge Trips
POST /api/v1/trips/:id/merge
Content-Type: application/json
{ "source_trip_id": "uuid-of-trip-to-merge-in" }Merges items from the source trip into the target trip.
Trip Status
GET /api/v1/trips/:id/statusReturns processing status for the trip.
Demo Trip
GET /api/v1/trips/demoReturns a sample trip for onboarding — no auth required.
Items
Get Single Item
GET /api/v1/items/:idResponse: { "data": <item> } — full Item shape with details_json containing confirmation numbers, seat assignments, etc.
Update Item
PATCH /api/v1/items/:id
Content-Type: application/json
{ "summary": "Updated summary", "start_location": "Paris CDG" }Delete Item
DELETE /api/v1/items/:idAdd Item to Trip
POST /api/v1/trips/:id/items
Content-Type: application/jsonRequired fields: kind, start_date
All fields:
| Field | Type | Description |
|---|---|---|
kind | string | Required. One of: flight, hotel, car_rental, train, activity, restaurant, ticket, other |
start_date | string | Required. ISO date: YYYY-MM-DD |
end_date | string | ISO date. For hotels = checkout, flights = arrival date if different |
start_ts | string | ISO 8601 datetime with timezone: 2026-04-01T08:30:00Z |
end_ts | string | ISO 8601 datetime with timezone |
start_location | string | Departure/origin. City, airport code, or address (max 300 chars) |
end_location | string | Arrival/destination (max 300 chars) |
summary | string | One-line summary, e.g. "AF276 CDG→NRT" (max 1000 chars) |
provider | string | Airline, hotel chain, etc. e.g. "Air France" (max 200 chars) |
confirmation_code | string | Booking reference (max 200 chars) |
traveler_names | string[] | Array of traveler names (max 20, each max 200 chars) |
details_json | object | Freeform metadata — gate, seat, room type, etc. (max 10KB) |
notes | string | User notes |
status | string | Item status |
Example — Flight:
{
"kind": "flight",
"start_date": "2026-04-01",
"start_ts": "2026-04-01T08:30:00+01:00",
"end_ts": "2026-04-01T15:45:00+09:00",
"start_location": "Paris CDG",
"end_location": "Tokyo NRT",
"summary": "AF276 CDG→NRT",
"provider": "Air France",
"confirmation_code": "XK7J3M",
"traveler_names": ["Ian Rogers"],
"details_json": { "flight_number": "AF276", "seat": "14A", "class": "Economy" }
}Example — Hotel:
{
"kind": "hotel",
"start_date": "2026-04-01",
"end_date": "2026-04-05",
"start_location": "Tokyo, Japan",
"summary": "Park Hyatt Tokyo",
"provider": "Hyatt",
"confirmation_code": "HY-889923",
"traveler_names": ["Ian Rogers", "Hedvig Rogers"],
"details_json": { "room_type": "King Deluxe", "check_in": "15:00", "check_out": "11:00" }
}Example — Train:
{
"kind": "train",
"start_date": "2026-04-05",
"start_ts": "2026-04-05T09:00:00+09:00",
"end_ts": "2026-04-05T11:30:00+09:00",
"start_location": "Tokyo Station",
"end_location": "Kyoto Station",
"summary": "Shinkansen Nozomi 7",
"provider": "JR Central",
"confirmation_code": "JR-44521",
"details_json": { "car": "7", "seat": "3A", "class": "Green Car" }
}Example — Restaurant:
{
"kind": "restaurant",
"start_date": "2026-04-03",
"start_ts": "2026-04-03T19:00:00+09:00",
"start_location": "Sukiyabashi Jiro, Ginza, Tokyo",
"summary": "Dinner at Sukiyabashi Jiro",
"details_json": { "party_size": 2, "reservation_name": "Rogers" }
}Example — Ticket/Event (concert, sports, theater, festival, etc.):
{
"kind": "ticket",
"summary": "David Byrne at Théâtre du Châtelet",
"start_date": "2026-05-15",
"start_ts": "2026-05-15T20:00:00+02:00",
"start_location": "Paris",
"provider": "Ticketmaster",
"details_json": {
"event_name": "David Byrne: American Utopia",
"venue": "Théâtre du Châtelet",
"venue_address": "1 Place du Châtelet, 75001 Paris",
"performer": "David Byrne",
"event_time": "20:00",
"door_time": "19:00",
"section": "Orchestre",
"seat": "12",
"row": "G",
"ticket_count": 2,
"ticket_type": "Reserved",
"event_category": "concert"
}
}Ticket detail fields:
| Field | Type | Description |
|---|---|---|
| event_name | string | Name of the event/show |
| venue | string | Venue name |
| venue_address | string? | Full address |
| event_time | HH:MM | Show start time |
| door_time | HH:MM? | Door opening time |
| section | string? | Seating section |
| seat | string? | Seat number |
| row | string? | Row identifier |
| ticket_count | number | Number of tickets |
| ticket_type | string? | GA, Reserved, VIP, etc. |
| performer | string? | Artist/performer/team |
| event_category | enum | concert, theater, sports, museum, festival, other |
Supported ticket providers: Ticketmaster, AXS, Eventbrite, Dice, SeeTickets, StubHub, Viagogo, venue direct sales. Forward the confirmation email to trips@ubtrippin.xyz and the ticket is extracted automatically.
Event-driven trips: When a ticket email creates a new trip (no overlapping dates), the trip is named after the event/performer and the cover image is of the performer — not the city.
Batch Add Items
POST /api/v1/trips/:id/items/batch
Content-Type: application/json
{ "items": [ <item>, <item>, ... ] }Up to 50 items per request. Same fields as single item creation above.
Response: { "data": [...items], "meta": { "count": N } }
Tip for agents: When your user gives you a booking confirmation (email text, screenshot, pasted text), parse it yourself and use these endpoints to add structured items. You handle the extraction; UBTRIPPIN handles the storage, grouping, and display.
Item Status
GET /api/v1/items/:id/statusRefresh Item Status
POST /api/v1/items/:id/status/refreshRe-checks live status (e.g. flight delays, gate changes).
Loyalty Vault
List My Loyalty Programs
GET /api/v1/me/loyaltyResponse:
{
"data": [
{
"id": "uuid",
"provider_key": "delta_skymiles",
"provider_name": "Delta SkyMiles",
"member_number": "1234567890",
"tier": "Gold",
"notes": null
}
]
}Lookup by Provider
GET /api/v1/me/loyalty/lookup?provider_key=delta_skymilesReturns matching loyalty entry for a specific provider.
Add Loyalty Program
POST /api/v1/me/loyalty
Content-Type: application/json
{ "provider_key": "delta_skymiles", "member_number": "1234567890", "tier": "Gold" }Update Loyalty Program
PATCH /api/v1/me/loyalty/:id
Content-Type: application/json
{ "member_number": "9876543210", "tier": "Platinum" }Delete Loyalty Program
DELETE /api/v1/me/loyalty/:idExport Loyalty Data
GET /api/v1/me/loyalty/exportReturns all loyalty data in a downloadable format.
List Known Providers
GET /api/v1/loyalty/providersReturns the full list of supported loyalty providers (no auth required).
Profile
Get My Profile
GET /api/v1/me/profileResponse includes name, email, preferences, tier, and settings.
Update My Profile
PUT /api/v1/me/profile
Content-Type: application/json
{ "display_name": "Ian Rogers", "timezone": "Europe/Paris" }Also accepts POST with the same body.
Family
List My Families
GET /api/v1/familiesCreate Family
POST /api/v1/families
Content-Type: application/json
{ "name": "The Rogers Family" }Get Family
GET /api/v1/families/:idUpdate Family
PATCH /api/v1/families/:id
Content-Type: application/json
{ "name": "Updated Family Name" }Delete Family
DELETE /api/v1/families/:idInvite Member to Family
POST /api/v1/families/:id/members
Content-Type: application/json
{ "email": "partner@example.com", "role": "member" }Remove Family Member
DELETE /api/v1/families/:id/members/:uidFamily Member Profiles
GET /api/v1/families/:id/profilesFamily Trips
GET /api/v1/families/:id/tripsReturns all trips visible to family members.
Family Loyalty Programs
GET /api/v1/families/:id/loyaltyFamily Loyalty Lookup
GET /api/v1/families/:id/loyalty/lookup?provider_key=delta_skymilesLook up a loyalty number across all family members.
Family City Guides
GET /api/v1/families/:id/guidesFamily Invites
GET /api/v1/family-invites/:token
POST /api/v1/family-invites/:token/acceptView and accept family invite links.
Collaborators (Trip Sharing)
List Collaborators
GET /api/v1/trips/:id/collaboratorsInvite Collaborator
POST /api/v1/trips/:id/collaborators
Content-Type: application/json
{ "email": "friend@example.com", "role": "viewer" }Update Collaborator Role
PATCH /api/v1/trips/:id/collaborators/:uid
Content-Type: application/json
{ "role": "editor" }Remove Collaborator
DELETE /api/v1/trips/:id/collaborators/:uidTrip Invites
GET /api/v1/invites/:token
POST /api/v1/invites/:token/acceptView and accept trip collaboration invite links.
City Guides
List Guides
GET /api/v1/guidesQuery params: ?family_id=uuid (optional)
Create Guide
POST /api/v1/guides
Content-Type: application/json
{ "city": "Tokyo", "title": "Tokyo Eats" }Get Guide
GET /api/v1/guides/:idUpdate Guide
PATCH /api/v1/guides/:idDelete Guide
DELETE /api/v1/guides/:idList Guide Entries
GET /api/v1/guides/:id/entriesAdd Guide Entry
POST /api/v1/guides/:id/entries
Content-Type: application/json
{ "name": "Tsukiji Outer Market", "category": "food", "notes": "Go early" }Update Guide Entry
PATCH /api/v1/guides/:id/entries/:eidDelete Guide Entry
DELETE /api/v1/guides/:id/entries/:eidNearby Guides
GET /api/v1/guides/nearby?lat=35.6762&lng=139.6503Find guides near a location.
Senders (Allowed Email Addresses)
List Senders
GET /api/v1/settings/sendersAdd Sender
POST /api/v1/settings/senders
Content-Type: application/json
{ "email": "mywork@company.com" }Remove Sender
DELETE /api/v1/settings/senders/:idCalendar
Get Calendar Token
GET /api/v1/calendar/tokenReturns an iCal subscription URL for syncing trips to calendar apps.
Regenerate Calendar Token
POST /api/v1/calendar/tokenInvalidates the old token and generates a new one.
Notifications
List Notifications
GET /api/v1/notificationsQuery params: ?unread=true (optional)
Mark Notification Read
PATCH /api/v1/notifications/:id
Content-Type: application/json
{ "read": true }Webhooks
List Webhooks
GET /api/v1/webhooksCreate Webhook
POST /api/v1/webhooks
Content-Type: application/json
{ "url": "https://example.com/hook", "events": ["trip.created", "item.added"] }Get Webhook
GET /api/v1/webhooks/:idUpdate Webhook
PATCH /api/v1/webhooks/:id
Content-Type: application/json
{ "url": "https://example.com/new-hook", "active": true }Delete Webhook
DELETE /api/v1/webhooks/:idTest Webhook
POST /api/v1/webhooks/:id/testSends a test payload to verify the endpoint.
Webhook Deliveries
GET /api/v1/webhooks/:id/deliveriesLists recent delivery attempts with status codes.
Trains
Train Status
GET /api/v1/trains/:trainNumber/statusReturns real-time status for a train by number (delays, platform, etc.).
Images
Search Images
GET /api/v1/images/search?q=tokyo+towerSearch for destination/cover images.
Imports
List Imports
GET /api/v1/importsCreate Import
POST /api/v1/importsUpload booking data for batch import.
Get Import
GET /api/v1/imports/:idBilling
Get Subscription
GET /api/v1/billing/subscriptionReturns current plan, tier, and billing period.
Get Billing Portal URL
GET /api/v1/billing/portalReturns a Stripe billing portal link for managing subscription.
Get Prices
GET /api/v1/billing/pricesReturns available plans and pricing.
Checkout
POST /api/v1/checkout
Content-Type: application/json
{ "price_id": "price_xxx" }Creates a Stripe checkout session.
Activation
Check Activation Status
GET /api/v1/activation/statusReturns whether the user's account is activated.
Adding New Bookings (Email Forwarding)
The primary way to add bookings is email forwarding. When your user receives a booking confirmation:
- Forward the email to: trips@ubtrippin.xyz
- Must forward from their registered sender address — UBTRIPPIN rejects unknown senders.
- UBTRIPPIN's AI parser extracts the booking details automatically (usually within 30 seconds).
- The item appears in the relevant trip (or a new trip is created).
How to do this as an agent:
- Use your email sending capability to forward the email from the user's address to trips@ubtrippin.xyz.
- Or instruct the user to do it manually from their inbox.
- PDF attachments (e.g. eTickets) are supported — include them in the forward.
Works with: flights, hotels, trains (Eurostar, SNCF, Thalys, etc.), rental cars, ferry bookings, concert/event tickets (Ticketmaster, AXS, Eventbrite, Dice, SeeTickets, StubHub, Viagogo), and most major booking platforms (Booking.com, Expedia, Kayak, Trainline, etc.).
Typical Agent Workflows
"What trips do I have coming up?"
GET /api/v1/trips- Filter by start_date >= today
- Format and present
"What's my itinerary for Tokyo?"
GET /api/v1/trips— find the Tokyo trip IDGET /api/v1/trips/:id— get full itinerary with all items- Format chronologically by start_ts
"I just booked a hotel in Tokyo — add it"
- Ask the user to forward the confirmation email from their registered address to trips@ubtrippin.xyz
- Or if you have email access: forward it yourself
- Wait ~30 seconds, then
GET /api/v1/trips/:idto confirm it appeared
"What's my Delta SkyMiles number?"
GET /api/v1/me/loyalty/lookup?provider_key=delta_skymiles- Return the
member_numberfrom the response
"Add my Marriott Bonvoy membership"
POST /api/v1/me/loyaltywith{ "provider_key": "marriott_bonvoy", "member_number": "123456789" }
"What loyalty programs does my family have for Delta?"
- Get the family ID:
GET /api/v1/families GET /api/v1/families/:id/loyalty/lookup?provider_key=delta_skymiles- Returns all family members' Delta numbers
"Add my family members"
POST /api/v1/familiesto create a family group (if none exists)POST /api/v1/families/:id/memberswith{ "email": "partner@example.com" }for each member- They'll receive an invite email to accept
"Share my trip with a friend"
POST /api/v1/trips/:id/collaboratorswith{ "email": "friend@example.com", "role": "viewer" }
"Is my train on time?"
GET /api/v1/trains/:trainNumber/status- Report delays, platform changes, etc.
"Show me city guides near me"
GET /api/v1/guides/nearby?lat=48.8566&lng=2.3522
"Set up a webhook for new bookings"
POST /api/v1/webhookswith{ "url": "https://...", "events": ["item.added"] }
"Get me a calendar link for my trips"
GET /api/v1/calendar/token- Give the user the iCal URL to add to their calendar app
Error Handling
| Status | Code | Meaning |
|---|---|---|
| 401 | unauthorized | Missing/invalid API key |
| 400 | invalid_param | Bad UUID or missing field |
| 404 | not_found | Trip/item not found or belongs to another user |
| 429 | _(body varies)_ | Rate limited — wait 60s |
| 500 | internal_error | Server error — retry once |
All errors return: { "error": { "code": "...", "message": "..." } }
Notes for Agents
- All IDs are UUIDs.
- Dates are ISO 8601 (
YYYY-MM-DDfor dates,YYYY-MM-DDTHH:MM:SSZfor timestamps). details_jsoncontains raw parsed data — useful for confirmation numbers, seat assignments, loyalty numbers, etc.confidence(0–1): how confident the AI parser was. Items withneeds_review: truemay have errors.- The API key is the user's — never share it, log it, or store it beyond the session unless the user explicitly asks.
Managing API Keys
Users manage keys at ubtrippin.xyz/settings. Each key has a name and a masked preview. If a key is compromised, the user can revoke it from the settings page and generate a new one.