engine_unsupported_feature — Other engine only
What the API returns
{
"error": {
"code": "engine_unsupported_feature",
"message": "The engine of this channel does not support that feature.",
"request_id": "req_01JRQ8F4X9N2K7YB3C5V6W8H0T"
}
}Every Wapito error is this one envelope. Branch on code, which is stable; message is written for people and can be reworded; details appears only when there is something specific to say; request_id is what to quote to support.
What it means
engine_unsupported_feature is an HTTP 501 error from the Wapito WhatsApp API: other engine only. The response message reads “The engine of this channel does not support that feature.” It is not retryable: the same request fails again until you change it. 5 endpoints can raise it, GET /messages/list/{chat_id} among them.
Why it happens
Every channel runs on one of two WhatsApp engines, and a handful of operations only exist on one of them: reading message history and chat lists, starring, forwarding, listing contacts and presences, deleting a channel. The endpoint is real and works, but not on the engine this channel is linked with. The answer carries details.engine, the capability that was asked for, and details.hint naming the engine that has it. Nothing about the request is wrong, so retrying it on the same channel will answer the same way.
How to fix engine_unsupported_feature
Read details.hint: it names the other engine and the dashboard action that switches the channel to it, which relinks the number by QR or pairing code.
Check the availability badge on the endpoint's reference page before building on it, so the engine choice is made once per channel rather than discovered in production.
If you need features from both engines, run two channels on two numbers rather than switching one channel back and forth; each switch is a relink.
Endpoints that raise it
Where you will meet it
- Create Channel
Feature guide
Retry guidance
Do not retry as sent
The same request fails the same way until something changes: the body, the credential, the recipient or the state of the channel. Keep it off every retry loop, fix the cause above, and send a corrected request once.
Frequently asked questions
Which engine should a new channel use?
The default engine covers everything most integrations need - sending, groups, channels, stories, polls, webhooks - and is the lighter of the two. Pick the other one only when a page in the reference marks the operation as available on it alone, such as message history or chat listing, and expect a QR relink when you switch.
Is engine_unsupported_feature the same as feature_not_available?
No. This 501 means the other engine can do it and the hint tells you how to get there. feature_not_available is the 501 for operations neither engine supports yet; those are published in the contract for the next phase and answer the same way on every channel until they ship.
Related
Try it on your own number
Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.