Org Web Adapter

Editing hungryroot/jira/be_6504_client_migration_doc_followup_get_api_get_tag_group.org

:PROPERTIES:
:ID:       c59a475f-00dc-4dc7-ace6-a109592c9026
:END:
#+title: BE-6504 Client migration doc followup GET /api/get_tag_group/

- source :: https://hungryroot.atlassian.net/browse/BE-6504
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]] 
- epic   :: [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:211bb652-f918-4774-9611-ec6c3a77c72b][HR BE Sprint 105]]
- status :: [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

* Tasks
** DONE Review current stats and update Confluence doc for /api/get_tag_group :sprint105:ep411:be6504:work:hungryroot:apiv1:v1migration:docs:admin:
:PROPERTIES:
:ID:       40bca748-1c27-67f0-a987-a22dafd5be80
:END:

* Description
Over time, we've been creating DRF powered "v2" endpoints (routes are prefixed
with /api/v2/) that allow for out-of-the box API contract discovery and
documentation through the drf-spectacular swagger interface. We want to migrate
away from v1 endpoints (v1 routes don't have a version prefix, just /api/) defined
in app/urls/apiv1.py

Analyze whether the "v1" GET /api/get_tag_group/ endpoint has a "v2" DRF
equivalent under the app/rest/ directory. If it does, explain differences in the
API contracts: both responses and supported request body fields and/or query
params between the two.

Acceptance criteria:

[ ] Update the v1 -> v2 migration Confluence doc for the specified section:
https://hungryroot.atlassian.net/wiki/spaces/BA/pages/889749506/v1+-+v2+API+migration+guide#GET-/api/get_tag_group/