Myntra PPMP API V4 Order Transition

Short Brief for Freelancer
Problem in one paragraph
We have a Myntra PPMP API V4 integration through our seller/OMS system. Order 5f91f476-567e-46c4-beb5-99079ba870e2, release ID 100256043698, remains in RFR. Get Order by ID works successfully and confirms status_code = RFR. Ready To Dispatch fails because Myntra says the release is RFR and must first be in Work in Progress. Myntra previously informed us that our order response was being returned in HTML instead of JSON, causing orders to remain in RFR. We have corrected our implementation, but this existing order is still RFR. We need an experienced Myntra PPMP/OMS/API developer to trace the original Myntra → OMS transaction, verify the response sent to Myntra, identify the exact RFR → WIP transition mechanism, determine whether Myntra needs to replay/reprocess the order, and make/validate any required changes so that a new order can successfully progress from RFR → WIP → RTD.
Required experience
The freelancer should have practical experience with:
• Myntra Seller/Partner APIs
• Myntra PPMP
• Myntra PPMP API V4
• Order lifecycle/status management
• RFR/WIP/RTD workflow
• REST APIs
• JSON/API response handling
• HTTP headers and Content-Type
• Webhook/event debugging
• OMS integration
• Unicommerce / SELLWELL / similar OMS
• Warehouse/facility mapping
• SKU/listing mapping
• Production API troubleshooting
Desired outcome
We need someone who can actually trace the API transaction and identify the root cause, rather than only testing the Get Order and RTD APIs in Postman.
The final outcome should be a working end-to-end flow:
Myntra
↓
Order Event
↓
SELLWELL / OMS
↓
Correct JSON Response
↓
Myntra
↓
WIP
↓
RTD
↓
Successful Dispatch