Get a specific product (Baileys engine only)
GET/api/sessions/:sessionId/catalog/products/:productId
Get a specific product (Baileys engine only)
Request
Responses
- 200
- 404
- 409
- 501
- 503
The product, or an empty body when no product in the catalog carries that id.
No session is running under that id — it was never started, was stopped, or does not exist. These routes report an unstarted session as 404, where the message and group routes report it as 400.
The session is not connected — an engine exists for it but is not ready: disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A session that was never started answers 400 instead, and the session lifecycle routes answer 409 for a conflicting state rather than this. One window answers this while the session still reads ready: WhatsApp Web periodically reloads its own page and the engine re-injects into it — for those few seconds the answer is a 409 naming the reload; retry shortly.
Not supported by the active engine: whatsapp-web.js has no catalog API.
WhatsApp did not answer the catalog query within the request budget — retry shortly.