plan_feature_required

The plan does not include this capability at all. Unlike a quota, nothing about it resets — only a different plan changes the answer.

• Opening a client workspace on a plan below Agency.
• Pinning a model above the plan's tier to an assistant.
• Sending a WhatsApp alert after the five-message trial, on a plan without WhatsApp.

• `details.feature` names the capability and `details.required_plan` the cheapest plan that includes it.
• Upgrade to that plan, or use the alternative the plan does have — Telegram alerts are unlimited on every tier.
• `GET /api/billing/entitlements` answers the same question in advance, so a control can be shown locked rather than failing on submit.

{
  "error": {
    "code": "plan_feature_required",
    "message": "The plan does not include this capability at all. Unlike a quota, nothing about it resets — only a different plan changes the answer",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/plan_feature_required",
  "title": "Plan Feature Required",
  "status": 402,
  "detail": "The plan does not include this capability at all. Unlike a quota, nothing about it resets — only a different plan changes the answer",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• quota_exceeded

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.