Partners and white-label
Run it for your customers, under your own name.
For agencies with many brands, and for platforms that want marketing inside their product. Give each customer a workspace, sign them in from your app, and show their results in your pages.
Marketing
Trail Races · last 30 days
An invented platform, “Trailbook”, showing an embedded overview in its own colour.
White-label
Your colour, your logo. Our engine.
The views and the app carry your account’s name, logo and main colour. On the Agency plan, the “Powered by SoldOut OS” line disappears.
How it works
Three requests. That is the integration.
-
1
A workspace for each customer
One request creates it, keyed on your own customer id. Call it every time a customer opens your marketing page: the same id returns the same workspace and changes nothing.
POST https://api.soldout-os.com/api/v1/partner/workspaces { "external_ref": "customer-42", "name": "Trail Races", "vertical": "events", "currency": "EUR" } -
2
Sign them in from your product
Your user is already signed in on your side. Ask for a link and send their browser to it. It works once, for sixty seconds, and they never see a second password.
POST https://api.soldout-os.com/api/v1/partner/sso { "workspace_id": "…", "role": "marketer", "user": { "external_ref": "user-7", "email": "ana@customer.com" } } -
3
Show their results in your pages
Read-only views for your own site: every active offer and how far it is towards its goal, or one offer in detail. They carry your name, your logo and your colour.
POST https://api.soldout-os.com/api/v1/partner/embeds { "workspace_id": "…", "view": "overview", "ttl": 900 } <iframe src="{url}" style="border:0;width:100%;height:420px"></iframe>
Safeguards
Built so trust cannot be borrowed.
Your word cannot open someone else’s account
You can sign in only people who exist because of you. If an address already has an account outside your organisation, the request is refused.
Views that cannot change anything
The embedded views have no session behind them. You name the sites that may frame them; until you do, they can be framed nowhere.
Your customers stay apart
Each customer is a workspace of its own, separated in the database. Suspending one keeps its data and closes its door.
The whole API, for every customer
With the same key and one extra header, you can use every endpoint inside any of your workspaces.
Not here yet
So you can plan around it.
- Your own domain for the app and for e-mail
- Signing in with SoldOut OS from your product (today your server calls ours)
- Libraries for PHP and JavaScript
- More embedded views: results by source, recommendations
- Ready-made connectors for ticketing and shop platforms
Questions
Asked and answered.
Who is this for?
Agencies that run ads for several brands, and platforms (ticketing, booking, shop or website builders) that want marketing inside their own product.
Can our customers see SoldOut OS?
In the embedded views they see your name, logo and colour. On the Agency plan the “Powered by SoldOut OS” line is removed. Custom domains are not available yet.
How do we get a partner key?
Partner keys are issued by our team. Tell us about your customers and we set one up with you.
What do our customers pay?
You agree that with us: per workspace, or as one account for everything you run.
Tell us about your customers.
How many brands, what they sell, where their sales are recorded. We answer with a key and a plan that fits.