When you’d use this
If you onboard client organizations throughPOST /v1/organizations, every client starts on default pricing. A tier lets you move a specific client onto terms you negotiated with us, without asking us to edit anything per client.
Typical reasons to reach for it:
- A high-volume client you quoted a tighter rate to.
- A segment of your book that carries a wider spread and pays you a larger share.
- Repricing a client whose volume has changed since onboarding.
What a tier is
A tier is two related numbers:
The two move together. A wider spread is what funds a larger referral share, which is why both are part of the same negotiated tier rather than two independent dials.
Your client sees the spread on their own quotes. They never see the referral share.
Tiers are defined by Nxos and agreed with you up front. You can list and assign them; you cannot create or edit them.
GET /v1/sub-org-tiers returns only the tiers agreed with your organization, so a tier negotiated with another broker is never visible to you.
Listing the tiers you can assign
403 forbidden. Contact us to turn it on.
Assigning a tier
Name the client with theNxos-On-Behalf-Of header and pass the tier’s key:
null to remove the tier and return the client to default pricing:
GET /v1/organizations with the same header. The response carries a subOrgTier field, null when the client is on default pricing.
referrerShareBps is included only when you read the client, through Nxos-On-Behalf-Of. If that client reads its own organization with its own API key it sees key, label and spreadBps, but not the share you earn. Your client sees the spread it is charged, never your referral.
Who can assign what
You may only set the tier of an organization you created throughPOST /v1/organizations. Holding an LOA is not enough, which is what stops a client repricing itself while acting on its own behalf.
You do not need to wait for verification. Terms are agreed at onboarding, so you can price a client from the moment you create them.
Setting a tier works before KYB, but reading one back does not. Until a client’s verification is
APPROVED, GET /v1/organizations with Nxos-On-Behalf-Of returns 403 authorization_required.That is expected, not a failed write. The response to PUT /v1/organizations/sub-org-tier echoes the tier it stored, so use it as your confirmation.