Authorize by link / connected accounts map via API#1420

Problem: after user creates authorize by link + access token, there’s no API end point to return accounts linked in that session, meaning I need to create a manual map for swim lanes between advertiser credentials.

• https://onboard.windsor.ai/api/team/generate-co-user-url/?{apiKey} only returns url w/ access token, no member_name returned
• https://onboard.windsor.ai/api/ds/accounts/{connector}?api_key={apiKey}
  returns member_name, no access token returned; member_name also not returned for every account connected via authorize by link, often null

Solution Needed: map via API that returns link + access token AND account IDs. I assume the simplest way would be to send Windsor access token from authorize by link in https://onboard.windsor.ai/api/ds/accounts/{connector}?api_key={apiKey} response

Also hide the access to the chat when an external user access the app using the authorization link.

I want to know how much longer it will take for this feature to go live.

@Jay Wong @Jay Wong can you describe why you need this? What is the exact use case?

Exact use case is for user to have streamlined onboarding flow and start pulling data right away. Now, user creates account via authorize link and then they need to wait for us to manually map the accounts they just connected to the user, breaking the onboarding flow. If we can connect the link they used to add connectors to the accounts they connected, then we no longer have to do that manual mapping.

Thanks again for your support so far.

I would like to describe a concrete feature we need and the reason behind it.

Our setup
We have one main Windsor account.
Under this main account, we use multiple Windsor sub‑accounts.
Each sub‑account is used to serve and manage the Facebook ad accounts of a different advertising company/client.
For each client, we send them a separate external authorization link (from the corresponding sub‑account), so that their Facebook Ad Accounts are connected under the correct Windsor sub‑account.
The problem
After a Facebook Ad Account has been authorized via an external link, in Windsor we can see that this Ad Account is connected, but:

We cannot see through which Windsor account / which external authorization link this Facebook Ad Account was connected.

This creates a management problem for us:

We assign one Windsor sub‑account per client.
But when we look at the connected Facebook Ad Accounts, we have no direct way to know:
“This specific Facebook Ad Account belongs to which Windsor sub‑account?”
“Which client’s external link was used to authorize this account?”
Right now, the only way is to manually check and guess based on account names or data streams, which is:

time‑consuming,
error‑prone,
and not scalable as the number of clients and Ad Accounts grows.
What we would like Windsor to provide
We would really like a feature (UI and/or API) that allows us to clearly identify, for each connected Facebook Ad Account:

Which Windsor account / sub‑account it is associated with, and
Optionally, which external authorization link (or some identifier of that link) was used to connect it.
This could be:

An additional field in your API response for each Ad Account, or
A mapping endpoint we can query, or
A clearer indication in the Windsor UI that shows “this Ad Account is under sub‑account X”.
With this feature, we could:

Cleanly separate and manage the ad accounts of different client companies,
Avoid confusion about which accounts belong to which sub‑account,
And maintain a much clearer internal structure on top of Windsor.
Why this is important for us
Our core use case is to:

Use different Windsor sub‑accounts to manage different advertising companies,
Pull reporting data (performance, spend, balances, etc.) for each client separately,
And keep a clear mapping between:
Client company → Windsor sub‑account → Facebook Ad Accounts
Without this mapping information from Windsor, it becomes difficult to maintain and automate our management logic.

Could you please let us know:

Whether there is already any way to get this information (via UI or API) that we might have missed?
If not, whether you could consider adding such a feature or field to your product roadmap?
We believe this would also be useful for other partners who manage multiple clients through multiple Windsor accounts.

Thank you very much for considering this request, and I’m happy to provide more details or examples if needed.