> ## Documentation Index > Fetch the complete documentation index at: https://docs.barndoor.ai/llms.txt > Use this file to discover all available pages before exploring further. # Remove a model from a route group ## OpenAPI ````yaml /api-reference/openapi.yaml delete /api/llm-gateway/admin/model-route-groups/{id}/members/{alias} openapi: 3.1.0 info: title: Barndoor.ai Public API description: Unified public API specification for Barndoor.ai platform version: 2.18.0 servers: - url: https://{host} description: Barndoor public API variables: host: default: platform.barndoor.ai description: >- The host serving your Barndoor deployment. Defaults to production; override it for another environment or a dedicated deployment. security: - ApiKey: [] - OAuth2: - openid - profile - email tags: - name: dlp x-group: Data Control Center - name: identity x-group: Identity - name: llm-gateway x-group: LLM Gateway - name: notification x-group: Notifications - name: policy x-group: Policies - name: registry x-group: MCP Gateway - name: system-management x-group: Log Exports paths: /api/llm-gateway/admin/model-route-groups/{id}/members/{alias}: delete: tags: - llm-gateway summary: Remove a model from a route group operationId: remove_route_group_member parameters: - name: id in: path description: Identifier, a UUID required: true schema: type: string format: uuid - name: alias in: path description: Model alias required: true schema: type: string responses: '200': description: Deletion acknowledgement content: application/json: schema: $ref: '#/components/schemas/ModelRouteGroup' '401': description: Missing or invalid credentials '403': description: Caller is not permitted to act on this resource in this organization '404': description: No such resource in this organization components: schemas: ModelRouteGroup: allOf: - $ref: '#/components/schemas/ChangeAttribution' description: >- Who created and last changed this group, and why (BCP-3998). Group-level, not per member row: membership is edited as a *set* (`set_members` replaces the whole list), so "who added this one alias" is not a question the write path can answer, while "who last changed this group" is exactly what these columns record. - type: object required: - id - org_id - name - description - model_aliases properties: description: type: string id: type: string format: uuid model_aliases: type: array items: type: string description: >- Member aliases, alphabetical. Empty for a group nobody has filled in yet — which is a legitimate state, not an error: an admin can create the group, attach it to a policy, and populate it afterwards. name: type: string org_id: type: string format: uuid description: >- A route group plus its membership, which is how both the admin list and the routes table want it — the UI renders a chip per group on each route, so shipping the aliases with the group saves a second round trip and an inconsistent intermediate state. ChangeAttribution: type: object description: >- The attribution carried on an admin-configurable row, as returned to the portal. Every field is `Option` and nothing is backfilled: a row that predates V75 has no truthful actor to attribute it to, and inventing one would be worse than rendering a placeholder. Rows pick up attribution on their first write. properties: created_by_email: type: - string - 'null' created_by_name: type: - string - 'null' created_by_user_id: type: - string - 'null' format: uuid last_change_note: type: - string - 'null' description: >- Optional free text explaining *why* the last change was made ("Raised for the Q3 batch job", "Vendor deprecated the old endpoint"). Admin-authored and rendered in the portal, so it is untrusted input: length-capped here, escaped on render. last_modified_at: type: - string - 'null' format: date-time description: >- When the change named by `last_modified_by_*` happened. Its own column rather than the row's `updated_at`, because `updated_at` is bumped by writes nobody is attributed for -- pairing the two would date a named admin's edit to a background job's clock. See the V75 migration for the full reasoning. last_modified_by_email: type: - string - 'null' last_modified_by_name: type: - string - 'null' last_modified_by_user_id: type: - string - 'null' format: uuid securitySchemes: ApiKey: type: http scheme: bearer description: >- A Barndoor API key, sent as `Authorization: Bearer `. Keys are prefixed `bdai_` and are opaque — do not attempt to decode one. Interchangeable with an OAuth 2.0 access token. OAuth2: type: oauth2 x-issuer: https://auth.barndoor.ai/realms/barndoor description: >- An OAuth 2.0 access token from Barndoor's identity provider, sent as `Authorization: Bearer `. Public clients must use PKCE. Interchangeable with an API key. flows: authorizationCode: authorizationUrl: >- https://auth.barndoor.ai/realms/barndoor/protocol/openid-connect/auth tokenUrl: >- https://auth.barndoor.ai/realms/barndoor/protocol/openid-connect/token scopes: openid: Issue an OIDC ID token identifying the caller. profile: Read the caller's basic profile claims. email: Read the caller's email address. offline_access: Issue a refresh token. Optional — no operation requires it. clientCredentials: tokenUrl: >- https://auth.barndoor.ai/realms/barndoor/protocol/openid-connect/token scopes: openid: Issue an OIDC ID token identifying the caller. profile: Read the caller's basic profile claims. email: Read the caller's email address. offline_access: Issue a refresh token. Optional — no operation requires it. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.