Adobe User Management API | Community
Skip to main content
R
rares.mircea.m42
Level 1
February 23, 2026
Solved

Adobe User Management API

  • February 23, 2026
  • 1 reply
  • 36 views

We have an integration with the Adobe User Mgmt API which is pulling data from Product Profiles. Some of the groups we’ve been using have a “/” symbol in their name, and since the API uses the group’s name while building the request path, this turns out to be an incorrect URL.

We have tried URL encoding, but we receive 404 as well. One of the ideas we’ve thought of would be to use the deprecated API that uses group ids. Is there something we missed about group names?

https://adobe-apiplatform.github.io/umapi-documentation/en/api/getUsersByGroup.html

 

Thank you!

Best answer by AmitVishwakarma

Hi ​@rares.mircea.m42 

You didn’t miss anything: this is a known limitation of the User Management API when using group names in the getUsersByGroup path.
What’s going on

  • The endpoint is:GET /v2/usermanagement/users/{orgId}/{page}/{groupName}
  • The last segment is documented as {groupName}, but in reality it accepts either:
  • Group names containing / cannot be made to work reliably in this path:
    • A raw / breaks the URL and is interpreted as another path segment -> 404.
    • URL‑encoding it as %2F is still rejected by the API gateway and also returns 404.

Correct way to handle groups with /

  • Don’t switch to the deprecated API.
    • You can stay on the current getUsersByGroup endpoint.
  • Use the group ID instead of the group name in the last path segment, e.g.:
    • GET /v2/usermanagement/users/{orgId}/{page}/{groupId}
  • If you only have the name:
    • Call the groups listing endpoint (e.g. GET /v2/usermanagement/groups/{orgId}/{page}) to find the corresponding groupId, then
    • Call getUsersByGroup using that groupId.

 

1 reply

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity AdvisorAccepted solution
Community Advisor
March 4, 2026

Hi ​@rares.mircea.m42 

You didn’t miss anything: this is a known limitation of the User Management API when using group names in the getUsersByGroup path.
What’s going on

  • The endpoint is:GET /v2/usermanagement/users/{orgId}/{page}/{groupName}
  • The last segment is documented as {groupName}, but in reality it accepts either:
  • Group names containing / cannot be made to work reliably in this path:
    • A raw / breaks the URL and is interpreted as another path segment -> 404.
    • URL‑encoding it as %2F is still rejected by the API gateway and also returns 404.

Correct way to handle groups with /

  • Don’t switch to the deprecated API.
    • You can stay on the current getUsersByGroup endpoint.
  • Use the group ID instead of the group name in the last path segment, e.g.:
    • GET /v2/usermanagement/users/{orgId}/{page}/{groupId}
  • If you only have the name:
    • Call the groups listing endpoint (e.g. GET /v2/usermanagement/groups/{orgId}/{page}) to find the corresponding groupId, then
    • Call getUsersByGroup using that groupId.

 

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
    R
    rares.mircea.m42Author
    Level 1
    March 10, 2026

    Thank you very much for your detailed answer!

    I’ve checked the solution and it works. 

    Would it possible to have this known issue and workaround documented in the docs?

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      March 10, 2026

      ​@rares.mircea.m42 
      Glad to hear the workaround helped, and thanks again for validating it.  I completely agree this kind of limitation and workaround should be easier to find in the docs.  If the solution I shared resolved your issue, could you please mark it as the accepted answer? That way anyone else in the community who runs into the same problem will be able to find the fix more easily.

      Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
        Terms & ConditionsAccessibility statement

        Loading footer...