πŸ”’

Faye <> TravelJoy

Enter the shared password to view.

Faye <> TravelJoy Β· Referral partnership

Enhanced Partners V2

A cleaner way to sell on behalf of your agencies: referrals move off UTM tags and onto real IDs and a parent-company link β€” so every sale is attributed, and commissioned, correctly.

From labels β†’ IDs Agencies, self-serve via /enhanced-partners Agency commission + TravelJoy cut
What changes in V2

From UTM labels to IDs + parent company.

V1 inferred the selling agency from a utm_source label the request carried β€” a free-text string matched against a fixed list. V2 drops the label entirely: each advisor is registered against their agency once, and every sale simply carries that company-scoped advisor ID β€” validated against TravelJoy's parent-company link.

V1 Β· todayMatch a label, then translatefragile Β· string-matched
utm_source label"world-via"
β†’
Match a whitelistfixed list of agencies
β†’
Translate the advisorinternal id β†’ agency id
β†’
Attributeoverride + commission
V2 Β· newOne company-scoped advisor IDexplicit Β· validated
advisorIdcompany-scoped Β· from /v1/advisor
β†’
Validate parent-company linkis TravelJoy allowed to sell for it?
β†’
Attributeresolved advisor + commission
πŸ”—

The parent-company link

TravelJoy is the parent; each agency it sells for is a company linked beneath it. That link is the single source of truth for β€œwho can TravelJoy sell for” β€” it replaces the hardcoded whitelist, and it’s exactly what /enhanced-partners returns, each company with the advisor IDs you’ve created for it. No UTM string is ever consulted.

How a referral works

Look up the ID, refer, get paid.

Each advisor is registered against their agency once β€” so every sale just carries that advisor ID, and it's attributed to the right place.

1

Look up the advisor ID

Call GET /enhanced-partners for your companies, each with the advisorIds you've created for it.

2

Refer

Send that advisorId on the quote & purchase. The agency is already baked in β€” no company field needed.

3

Get paid

The agency earns its commission and TravelJoy earns its cut β€” attributed automatically.

API
# 1 Β· register an advisor for a company β€” referredCompanyId is optional, and mints the advisorId
POST /v1/advisor  { "firstName": "Dana", "lastName": "Levi", "referredCompanyId": 657 }
β†’ { "advisorId": "011238fa-a0cf-4275-88dd-ed7bfe4211ef" }

# 2 Β· list your companies with the advisor IDs you created for each
GET /enhanced-partners
[
  { "companyId": 657, "name": "TPI", "advisorIds": ["011238fa-…"] },
  { "companyId": 412, "name": "World Via", "advisorIds": ["7c2a…"] }
]

# 3 Β· refer the sale β€” just the advisorId
POST /v1/quote   { "advisorId": "011238fa-a0cf-4275-88dd-ed7bfe4211ef" }
Advisor attribution

Created once, reused every time.

The same logic in V1 and V2 β€” so an advisor’s commissions always land in the right place.

New
Registered for a company

POST /v1/advisor with a referredCompanyId mints the advisor’s company-scoped ID.

Returning
Every sale after

That same advisorId is reused β€” consistent, correct commissioning.

Advisor onboarding

From sign-up to selling in minutes.

An advisor goes from registering on TravelJoy to a live Faye seller in one short setup β€” no back-and-forth.

ExistingπŸ“Step 1

Register

The advisor signs up through TravelJoy.

β†’
Existing🎬Step 2

Watch the training

A short Faye training video gets them ready.

β†’
New🏷️Step 3

Pick the company

Choose an agency from the /enhanced-partners list.

β†’
ExistingπŸš€Live

Start selling

Quoting & selling on Faye, minutes later.

New company?

Agency not yet linked with Faye β†’ it enters a pending state. TravelJoy and Faye review and approve the link, then the advisor goes live.

What it takes to switch

A small change for you. The lift is on us.

Nothing about your setup gets harder. You swap one field; Faye builds and runs everything behind it.

Your side

Register advisors, send their ID

Same endpoints you already use β€” one small change.

  • Register advisors via POST /v1/advisor β€” now optionally with a referredCompanyId, which mints the advisor's company-scoped ID.
  • Call GET /enhanced-partners to get your companies and the advisor IDs you created for each.
  • Send just the advisorId on quotes & purchases β€” no utm_source tags, no per-sale company field.
  • Move onto Faye's V2 endpoints β€” same concepts, a few request changes β€” and unlock 3 plans (First, Forward & Flagship).
Small effort Β· guided by Faye
Faye's side

Everything behind the scenes

The heavy lifting stays with us, so the change stays invisible to your advisors.

  • Build the ID resolver and the parent-company link.
  • Set up each agency's advisor mapping up front.
  • Move every agency across and check each sale matches.
  • Retire the old UTM path once everything lines up.
Main lift Β· owned by Faye
How we roll it out

In stages β€” nothing breaks.

These are live, paid policies, so we move in steps and prove every sale attributes exactly as it does today before switching anything off. Your current integration keeps working the whole way.

Phase 1
Faye

Build the company list

We stand up the agency list behind /enhanced-partners. Nothing changes on your side yet β€” today's flow runs untouched.

Phase 2
Together

Switch to IDs

You register advisors with a referredCompanyId and send just the advisorId on each sale. Tags and IDs can run side by side while you cut over at your own pace.

Phase 3
Faye

Move every agency across

We migrate all agencies onto the new model and shadow-check that each sale attributes and prices exactly as before β€” so no commission ever lands in the wrong place.

Phase 4
Faye

Retire the old path

Once every agency matches, we switch off the UTM matching. From then on, referrals run entirely on IDs β€” and UTMs are no longer needed.

While you're here

You move to V2 β€” and gain more to sell.

Moving to V2 puts you on Faye's current API version and opens up more products. A small lift with real upside β€” and it gets you ahead of V1's retirement. It's a separate track from the ID change: the two ship independently, in whichever order suits you.

Today Β· V1

One product, winding down

1 planretiring 01.01.2027
β†’
With you Β· V2

Three plans, actively built

First Β· Forward Β· Flagshipnew features ship here
🎚️

More to sell

Offer three plans β€” First, Forward & Flagship β€” instead of one, so travelers pick the coverage that fits.

πŸ›‘οΈ

Future-proof

V2 is where new products and features land. Moving now means you grow with Faye instead of catching up later.

πŸͺΆ

Small lift

Same concepts you already use β€” a few request changes. We guide the migration end to end.

🧭 The move, in four steps
  1. Point your calls at the V2 endpoints β€” /v2/quote, /v2/purchase, /v2/quote/multi.
  2. Handle the three plans β€” First, Forward & Flagship β€” the quote returns the options; show them, or pick one.
  3. Everything else carries over β€” advisor registration and the IDs work exactly as they do today.
  4. We run V2 and V1 side by side, so you migrate at your own pace with nothing turned off early.
A lightweight rollout
Step 1
Build in sandbox
Integrate V2 + the 3 plans in staging.
Step 2
Pilot
Run V2 for a few advisors, alongside V1.
Step 3
Roll out
Move the rest of your traffic to V2.
01.01.2027
V1 retires
Fully on V2, ahead of deprecation.
Heads up

V1 is planned for deprecation on 01.01.2027. Moving to V2 as part of this change means one migration, done ahead of time β€” on the version that keeps getting better.

A few things to align on

Open questions for the TravelJoy team.

Quick decisions that shape the smoothest rollout β€” none are blockers.

01Confirm the advisor + company shape in V2.Today you register each advisor up front via POST /v1/advisor (declaring their annual Faye training) and pass that advisorId on every quote and purchase. In V2 you'd keep doing exactly that and add the company ID per sale β€” does that fit how your platform stores the advisor-to-agency relationship?
02How will you use /enhanced-partners?Would you rather pull the full company list once and cache it, or look one up per sale? We can support either.
03Who approves a new agency?When an agency isn't linked with Faye yet, who signs off on your side β€” and what turnaround should advisors expect before they go live?
04How do you want to start?Pilot with one or two agencies first, or move everyone together? And is there a window that works best for the switch?
05Ship the two changes separately?The referral / ID move and the V2 + 3-products move are independent. We'd suggest running them as two separate tracks so neither blocks the other β€” which order do you prefer, and would you rather space them out or do them in one window?
06Migrate your direct advisors too?Some advisors sell directly under TravelJoy rather than on behalf of another agency. Do you want those moved onto the new model as well, or should we start with only the agency-referred advisors?
Agency gets its commission TravelJoy gets its cut Attribution created once, reused every time

Faye Γ— TravelJoy Β· Enhanced Partners V2 Β· referral partnership overview