List catalog products (Baileys engine only)
GET/api/sessions/:sessionId/catalog/products
List catalog products (Baileys engine only)
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 501
- 503
One page of catalog products
A query value is invalid, or the query carries a field the DTO does not declare.
The API key is missing, unknown, revoked, or expired
WhatsApp refused the catalog query. Also returned when the API key's role, session or chat scope, or IP allow-list does not allow this operation.
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, meaning disconnected, reconnecting, or still initializing, so the request never reached WhatsApp. Wait for ready and retry. A send whose first attempt had already run when the session left ready (or WhatsApp Web reloaded its page) is the exception: it answers a 409 with no code that says the message may or may not have been sent, so check the chat before sending it again (a retry with the same Idempotency-Key answers IDEMPOTENCY_OUTCOME_UNKNOWN). 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, and until it has the answer is a 409 naming the reload, with code ENGINE_PAGE_RELOADING and retryAfterSeconds. That takes seconds on most reloads and can take a few minutes, and no event marks its end: ask again at that interval.
Not supported by the active engine: whatsapp-web.js has no catalog API.
WhatsApp did not answer the catalog query within the request budget, or rate-limited it. For some business accounts WhatsApp never answers it, so a retry may not help.