User expanded data from API?

[SimonBrown]

Hi

Looked at some other similar posts but not found an answer.

What API call can I use to get the highlighted user profile data?

I have looked at the user APIs and all available expand options to no avail.
Also checked a link shared in a similar post for the search APIs, but they do not document the fields and options at all well, just a few examples.

Is this some undocumented expand option or querystring parameter?

Thanks
Simon

[Hemanth]

Hi

Did you try /api/v2/users/{userId}

BR
Hemanth

[Eos_Rios]

What expands option provides the Office Address from that API Hemanth?

[SimonBrown]

I did, I mentioned in OP (although not which APIs)

I did try the user apis with the expand querystring option.
Looked at the deprecated users/{userId}/profiles as well as that appears to be one the GUI still uses (looking at Browser dev tools network tab)

Also ran over other APIs, including the search APIs, but as mentioned, the documentation on search options and fields is really quite limited, certainly in the API area.

First time not found something in the API myself, to my annoyance.

[tim.smith]

A lot of the profile fields aren't available via the Platform API for getting or updating. Here's the idea to vote on: https://genesyscloud.ideas.aha.io/ideas/OP-I-285.

[SimonBrown]

Shattered my view that Genesys is API ground up and everything you see is achievable via APIs

Voted anyway but that timeline is way off for my customer.

[tim.smith]

"Platform first" is true for the vast majority of existing features, and is heavily enforced for all new work. There are certain parts of the platform that have been there since the original inception of Genesys Cloud and aren't public for reasons that aren't appropriate for me to discuss here. The rewrite mentioned in the linked idea is addressing one of the key causes of non-public information in the platform. As you might expect, making big changes to how users are managed internally for such a large platform without breaking anything or changing any public-facing behavior is a significant task. But on the bright side, it's a task that's already underway.

This does leave you with some manual tasks, but we're continuing to push to get those gaps closed.

[SimonBrown]

Thanks for the explanation and I understand.
I will use the undocumented approach in the mean time.

Simon

[tim.smith]

Just a word of warning, undocumented API resources/parameters/features are not subject to the breaking change policy. This means that they may be changed or removed at any time without notice. This puts applications using those undocumented features at risk of a production outage when a breaking change is made.

[SimonBrown]

I get that. You will also be breaking it in your own UI as well as that's how it appears Genesys UI is doing it.
I would hope, unless you remove the feature in the UI, it will still become accessible with the replacement User API following the platform first ideology.
I have made the customer aware that this is undocumented and no guarantees.