Connect Myntra

1Find your Merchant ID and Secret Key

picoask reads your Myntra data through MMIP (Myntra's seller integration platform), using the Merchant ID and Secret Key Myntra issued you. picoask only reads — it never changes listings, inventory or fulfilment.

• Sign in to your Myntra seller account and open the MMIP developer area (mmip.myntrainfo.com).
• Under Developer / API, copy your Merchant ID and Secret Key.

The order-reconciliation API is available for PPMP Warehouse sellers. If your account is an Omni store, orders aren't exposed via this API — check your selling model with your Myntra category manager.

2Connect in picoask

In your project's Integrations tab, choose Myntra → Connect and fill in:

• Merchant ID — from step 1. It also scopes your data in the warehouse.
• Secret Key — from step 1.

picoask exchanges the pair for a read token the moment the connector starts provisioning, so a wrong Merchant ID or Secret Key is reported immediately. The Secret Key is stored encrypted and used only by the sync worker, which refreshes the token on its own.

3What gets synced

• Orders & lines — each order with its items: SKU/style, quantity, MRP, the seller and marketplace discount, tax and amount received.
• Returns — customer returns and RTO, dated by the return, so return rate is answerable.

Amounts land in ₹, exactly as reconciled. Per-order commission and marketplace fees are not in Myntra's API — those live only in the downloadable settlement reports — so take-home-after-fees isn't synced here; product-level revenue, discounts and returns are. Myntra exposes no traffic/impression data, so those metrics aren't available.

4Troubleshooting

• Credentials rejected — the Merchant ID or Secret Key was copied incompletely, or has been rotated. Recopy from MMIP → Developer / API and reconnect.
• No orders — order reconciliation is available for PPMP Warehouse sellers; an Omni account won't return orders here. Confirm your selling model with Myntra.