Enter the shared password to view.
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.
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.
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.
Each advisor is registered against their agency once β so every sale just carries that advisor ID, and it's attributed to the right place.
Call GET /enhanced-partners for your companies, each with the advisorIds you've created for it.
Send that advisorId on the quote & purchase. The agency is already baked in β no company field needed.
The agency earns its commission and TravelJoy earns its cut β attributed automatically.
# 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" }
The same logic in V1 and V2 β so an advisorβs commissions always land in the right place.
POST /v1/advisor with a referredCompanyId mints the advisorβs company-scoped ID.
That same advisorId is reused β consistent, correct commissioning.
An advisor goes from registering on TravelJoy to a live Faye seller in one short setup β no back-and-forth.
The advisor signs up through TravelJoy.
A short Faye training video gets them ready.
Choose an agency from the /enhanced-partners list.
Quoting & selling on Faye, minutes later.
Agency not yet linked with Faye β it enters a pending state. TravelJoy and Faye review and approve the link, then the advisor goes live.
Nothing about your setup gets harder. You swap one field; Faye builds and runs everything behind it.
Same endpoints you already use β one small change.
POST /v1/advisor β now optionally with a referredCompanyId, which mints the advisor's company-scoped ID.GET /enhanced-partners to get your companies and the advisor IDs you created for each.advisorId on quotes & purchases β no utm_source tags, no per-sale company field.The heavy lifting stays with us, so the change stays invisible to your advisors.
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.
We stand up the agency list behind /enhanced-partners. Nothing changes on your side yet β today's flow runs untouched.
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.
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.
Once every agency matches, we switch off the UTM matching. From then on, referrals run entirely on IDs β and UTMs are no longer needed.
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.
Offer three plans β First, Forward & Flagship β instead of one, so travelers pick the coverage that fits.
V2 is where new products and features land. Moving now means you grow with Faye instead of catching up later.
Same concepts you already use β a few request changes. We guide the migration end to end.
/v2/quote, /v2/purchase, /v2/quote/multi.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.
Quick decisions that shape the smoothest rollout β none are blockers.
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?Faye Γ TravelJoy Β· Enhanced Partners V2 Β· referral partnership overview