Org Web Adapter

Editing hungryroot/jira/be_6508_client_migration_doc_follow_on_post_api_reschedule_order.org

:PROPERTIES:
:ID:       aba7d856-f023-490a-ba45-70aff13c345d
:END:
#+title: BE-6508 Client migration doc follow on POST /api/reschedule_order/

- source :: https://hungryroot.atlassian.net/browse/BE-6508
- tags ::   [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]] 
- epic ::   [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:26939bb8-164c-402e-8a6a-6ae8c99d3e59][HR BE Sprint 102]] [[id:c82bb209-ab05-47b1-8f5d-3eebfb7a808a][HR BE Sprint 103]]
- status :: [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

** DONE Investigate V2 to find a matching endpoint for api/reschedule_order :work:hungryroot:api:docs:be6508:project:sprint103:ep411:
:PROPERTIES:
:ID:       d0b515d9-3990-47a8-a18f-bfe6471a6a43
: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" POST /api/reschedule_order/ 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#POST-/api/reschedule_order/