Share your published trip inventory
Trippy supports operator-assisted JSON and CSV feeds. Travellers book directly with you; a feed does not create a booking or verify available seats.
How imports work
- Contact Trippy with your official website, source identity and permission reference.
- Trippy verifies and pins your exact source and image hosts in a private import scope. Existing image restrictions still apply.
- Send a JSON array or CSV using the documented fields below. An authorised Trippy administrator validates a dry run before applying through the existing database credentials.
- Every record retains its successful source checked time. An upload never retires trips absent from that file.
No public unauthenticated write endpoint is available. Do not send credentials or traveller personal information in a feed.
Feed fields
- Required
- id, url, title, origin, destination, duration, price, currency, checked_at, price_unit, itinerary, start_date and future dates (dates). IDs must stay stable within your source.
- Evidence
- description and images. Mark units explicitly; do not substitute deposits or room prices for full-trip per-person amounts.
- Limits
- 500 records, 4 MiB per upload, HTTPS source URLs on your approved hosts. Unknown fields and invalid dates are rejected. Future checked timestamps and source identity changes are rejected.
Dates use YYYY-MM-DD. checked_at is an ISO timestamp for the actual successful source check. Prices are decimal strings in INR; scheduled dates do not confirm seats.