feature_not_available — Not available yet
What the API returns
{
"error": {
"code": "feature_not_available",
"message": "This feature is not available.",
"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
feature_not_available is an HTTP 501 error from the Wapito WhatsApp API: not available yet. The response message reads “This feature is not available.” It is not retryable: the same request fails again until you change it.
Why it happens
The operation is published in the contract but not implemented on either engine yet: communities, the business catalog and profile, interactive and carousel messages, quizzes, events, pinning, blocking, story listing and a few others are marked for the next phase and answer this status on every channel. The request was parsed and authenticated normally; it is the capability that is missing. details.capability names it and details.phase says which rollout phase brings it. No retry, engine switch or plan change gets a different answer today.
How to fix feature_not_available
Check the endpoint's availability in the API reference: an operation its tag hub lists as planned answers this code until the phase that ships it, and has no reference page of its own yet.
Build the flow on the operations that are available today and gate the planned call behind a feature flag, so switching it on later is a configuration change.
Watch the changelog for the phase that delivers the capability; the contract will not change shape when it does, only the status.
Endpoints that raise it
Where you will meet it
- Leave Group
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
Why publish an endpoint that answers 501?
So the contract, the SDKs and the reference are complete before the capability ships, and so a client written against the published shape keeps working the day it does. A planned operation validates its input exactly like a live one, which means the 501 is the only thing that changes when it goes live.
Would switching the channel to the other engine help?
No. This code is reserved for operations that neither engine implements yet, so the answer is the same on both. When a capability exists on one engine only you get engine_unsupported_feature instead, and that response carries a hint naming the engine that has it.
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.