Treppy / Travel Platforms and SaaS

Make insurance a native feature. Without building the infrastructure.

A white-labeled REST API for booking platforms, TMC systems, travel CRMs, and study-abroad or mission-trip tools. No carrier contracts, no compliance work, no redirects — just your brand, powered by Treppy, with revenue share on every policy sold.

• White-labeled API• Revenue share model• No redirects

Building an AI agent or copilot instead? See Treppy for AI Agent Builders →

quote.sh
POST /v1/quotes { "partner": "your-platform", "trip": "2026-05-02/09" } # returned under your brand, no Treppy mention 200 [ { plan: "Travel Medical", price: 38 }, { plan: "Trip Cancellation", price: 52 }, … bind, policy issues, revenue_share() tracked ]
White-labelBooking platformsTMC systemsTravel CRMs
One backend, invisible under the hood

The insurance layer your platform can white-label.

A clean partner API sits behind your product — your customers never see Treppy, only you.

White-labeled REST API

Quote, compare, bind, and issue behind one clean, versioned REST API — fully white-label, no Treppy branding visible to your customers.

POST /v1/quotes → compare → bind

Revenue share on every policy

Earn commission on every policy sold through your integration — a new recurring revenue line inside your platform.

policy.sold → revenue_share()

One contract, every carrier

Multiple A-rated carriers under a single integration and a single agreement. No per-carrier deals.

1 integration · N carriers

No infrastructure to build

No carrier contracts, no compliance layer, no quoting engine to build or maintain. We're the plumbing; your product is the experience.

0 carrier deals · 1 API
Built for travel software

If your customers are travel businesses, they already need this.

Booking platforms, TMC systems, travel CRMs, study-abroad portals, and mission-trip management tools all serve customers who need insurance — agents, retailers, institutions. Treppy becomes the infrastructure layer running invisibly inside your product.

  • Your customers get insurance without ever leaving your platform
  • You earn revenue share without building carrier relationships
  • Reaches the same profiles Treppy already serves — agents, retailers, institutions
// inside your platform, white-labeled const quotes = await treppy.quotes({ trip }) // → surfaced as your own "Protect this booking" feature await treppy.bind({ planId, partnerId: "you" }) // → policy issued under your brand, revenue share tracked
Booking platformsTMC systemsTravel CRMsStudy abroad portalsMission trip toolsCustom platforms
How it works

From key to revenue share in days.

01

Connect your platform

Grab API keys, sandbox, and an OpenAPI spec. Start testing quotes in minutes.

02

Embed it, white-labeled

Wire the REST API into your product. Your customers only ever see your brand.

03

Go live & earn

Your customers buy coverage inside your platform. You earn revenue share on every policy.

Why platforms choose Treppy

A new revenue line, none of the infrastructure.

White-label, always

Your customers never see Treppy — only your brand, on your platform.

Revenue share on every policy

A new recurring line inside your product, with no carrier work on your end.

One contract, every carrier

Multiple A-rated carriers, one agreement, one integration. Licensing and compliance handled behind it.

Serves your customers' customers

The same profiles Treppy already serves — agents, retailers, institutions — become reachable through your platform.

White-label · revenue share

Make insurance part of your platform.

A white-labeled API, multiple A-rated carriers, and revenue share on every policy — behind a single integration.