---
search:
  tags:
    - User Groups
    - GET
seo:
  description: >-
    Look up a single user group by its unique display name. Reference for the
    GET /v1/user-groups/name/{name} endpoint in the Roboto REST API.
sidebar:
  label: Get user group by name
  badge: GET
title: Get user group by name
type: openapi-operation
---
Look up a single user group by its unique display name.

Triggered when an operator (or the feature-flag admin flow) has a group name
in hand — typically the value typed into a "associate user group with this
flag" picker — and needs to resolve it to the current record before storing
the association. Raises ``RobotoNotFoundException`` if no group with that
name exists.

#### Access control
 - roboto_admin_only
 - Restricted tokens cannot call this endpoint

`GET /v1/user-groups/name/{name}`

**Responses**

- `200` — OK
- `400` — Thrown when the conversation context (messages, system prompt, tool results) exceeds the model's context window limit. The token estimate and the model's context limit are not carried on the exception, so a caller cannot read usage numbers off it.
- `401` — Thrown when authentication fails
- `403` — Thrown if an operation would exceed a user or org level limit.
- `404` — Thrown if a user is attempting to perform an action unrecognized by the Roboto platform.
- `409` — Thrown if there is a conflict between a resource you're creating and another existing resource
- `410` — Thrown if a resource is missing or expired.
- `500` — An error the platform reported that this SDK release cannot resolve to a specific exception class. Reported for an element of a :py:class:\`\~roboto.http.BatchResponse\` whose error names a code this release defines no class for, or that arrived without a code, without a message, or as text that is not an error envelope at all. It carries whatever code and message the platform sent, so a caller handling the failure still learns what went wrong; when no message could be read, the message is the error's raw text. The error envelope carries no status code, so \`\`http\_status\_code\`\` reports the 500 inherited from :py:class:\`RobotoDomainException\` rather than the status the failure actually had.
- `501` — Thrown by shimmed out APIs which have not yet been implemented
- `503` — Thrown when a service is unavailable, such as when it's under heavy load and can't accept new requests. This is expected to be transient and ought to be retried.
- `504` — Thrown when the service times out while processing a request. This is exepcted to be transient and ought to be retried.
- `507` — Thrown when the server cannot complete the request because the response payload exceeds a storage or transport capacity limit (e.g., Lambda response size). This is NOT expected to be transient and should NOT be retried.

Response example, 200:

```json
{
  "data": {
    "user_group_id": "string",
    "name": "string",
    "members": [
      "string"
    ],
    "created": "2019-08-24T14:15:22Z",
    "created_by": "string",
    "modified": "2019-08-24T14:15:22Z",
    "modified_by": "string"
  }
}
```