> For the complete documentation index, see [llms.txt](https://docs.mymedtrics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mymedtrics.com/api-reference/medtrics-classic-sis-bridge/group-tags.md).

# Group Tags

## GET /api/users/group-tags/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"ListEnvelope":{"type":"object","description":"Bridge-wide list envelope. count is always null and page_range always [] (cursor pagination upstream).","properties":{"count":{"type":["integer","null"]},"page_range":{"type":"array"},"per_page":{"type":"integer"},"next":{"type":["string","null"]},"previous":{"type":["string","null"]},"results":{"type":"array"}}},"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/":{"get":{"operationId":"groupTags_list","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","parameters":[{"name":"page","in":"query","schema":{"type":"integer"}},{"name":"page_size","in":"query","schema":{"type":"integer","maximum":100}},{"name":"id","in":"query","schema":{"type":"integer"},"description":"maps to Connect legacy_id"},{"name":"name","in":"query","schema":{"type":"integer"},"description":"maps to Connect name"},{"name":"active","in":"query","schema":{"type":"integer"},"description":"maps to Connect is_active"}],"responses":{"200":{"description":"ListEnvelope","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ListEnvelope"},{"type":"object","properties":{"results":{"type":"array","items":{"$ref":"#/components/schemas/GroupTags"}}}}]}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```

## POST /api/users/group-tags/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/":{"post":{"operationId":"groupTags_create","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","requestBody":{"content":{"application/json":{"schema":{"type":"object","properties":{"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GroupTags"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```

## GET /api/users/group-tags/{id}/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/{id}/":{"get":{"operationId":"groupTags_retrieve","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GroupTags"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```

## PUT /api/users/group-tags/{id}/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/{id}/":{"put":{"operationId":"groupTags_update","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","requestBody":{"content":{"application/json":{"schema":{"type":"object","properties":{"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GroupTags"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```

## DELETE /api/users/group-tags/{id}/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/{id}/":{"delete":{"operationId":"groupTags_destroy","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GroupTags"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```

## PATCH /api/users/group-tags/{id}/

> Legacy /api/users/group-tags/ bridge resource.\
> \
> Mirrors the \`group\_roles\` precedent but for institution-scoped group tags.\
> Unlike group\_roles, there is no program FK and no fan-out: each legacy\
> GroupTag maps 1:1 to an Oracle group\_tags row per institution.\
> \
> Legacy contract (GroupTagSerializer):\
> &#x20;   id          — integer legacy PK (from etl\_id\_registry.source\_id via IdFieldRemap)\
> &#x20;   name        — tag name\
> &#x20;   active      — boolean (maps from Connect is\_active)\
> &#x20;   group\_count — integer (number of groups assigned to this tag)\
> \
> Connect endpoints:\
> &#x20;   GET    /group-tags              → list\
> &#x20;   GET    /group-tags/{public\_id}  → detail (via ?legacy\_id=\<pk>\&limit=1 strategy)\
> &#x20;   POST   /group-tags              → create (institutional clients only)\
> &#x20;   DELETE /group-tags/{public\_id}  → soft-delete\
> \
> No fan-out note: legacy GroupTag is institution-scoped with no program FK.\
> The ETL creates one Oracle group\_tags row per legacy tag per institution.\
> No p\_canonical\_only filtering is needed; every row has a 1:1 legacy mapping.

```json
{"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"<client-name>","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token <hex>"},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"GroupTags":{"type":"object","description":"Legacy-shaped users/group-tags record as served by the bridge; translated from Connect /group-tags","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}},"paths":{"/api/users/group-tags/{id}/":{"patch":{"operationId":"groupTags_partial_update","tags":["GroupTags"],"description":"Legacy /api/users/group-tags/ bridge resource.\n\nMirrors the `group_roles` precedent but for institution-scoped group tags.\nUnlike group_roles, there is no program FK and no fan-out: each legacy\nGroupTag maps 1:1 to an Oracle group_tags row per institution.\n\nLegacy contract (GroupTagSerializer):\n    id          — integer legacy PK (from etl_id_registry.source_id via IdFieldRemap)\n    name        — tag name\n    active      — boolean (maps from Connect is_active)\n    group_count — integer (number of groups assigned to this tag)\n\nConnect endpoints:\n    GET    /group-tags              → list\n    GET    /group-tags/{public_id}  → detail (via ?legacy_id=<pk>&limit=1 strategy)\n    POST   /group-tags              → create (institutional clients only)\n    DELETE /group-tags/{public_id}  → soft-delete\n\nNo fan-out note: legacy GroupTag is institution-scoped with no program FK.\nThe ETL creates one Oracle group_tags row per legacy tag per institution.\nNo p_canonical_only filtering is needed; every row has a 1:1 legacy mapping.","requestBody":{"content":{"application/json":{"schema":{"type":"object","properties":{"name":{"type":"string","description":"Connect name"},"active":{"type":"string","description":"Connect is_active"},"group_count":{"type":"string","description":"Connect group_count"}}}}}},"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/GroupTags"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mymedtrics.com/api-reference/medtrics-classic-sis-bridge/group-tags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
