feature_not_enabled API Origin: Application & API Last updated 14 Oct 2026

API Error: Feature not enabled for this account (feature_not_enabled / not available on your plan)

The endpoint or option exists, but your account, plan, region or project hasn’t been granted access to it.

Exact message you may see This feature is not enabled for your accountnot available on your current planhas not been used in projectit is disabled. Enable it by visitingfeature is not available
Seen on: REST API

Meaning

Providers gate features behind plans, beta programmes, region availability or a setting in the dashboard. The API answers 403 (sometimes 400/402/404) with messages like “This feature is not enabled for your account”, “not available on your current plan”, or Google’s SERVICE_DISABLED (“API has not been used in project … or it is disabled”).

Common causes

  • Feature requires a higher plan or an add-on
  • Beta/preview feature not enabled for the account
  • Service/API not enabled in the cloud project
  • Feature not available in this region or for this account’s country
  • Using a test account without the capability

⚡ Quick fix

  1. Enable the feature/API in the provider dashboard or console
  2. Check plan and region availability
  3. Use an account or project where it is enabled

Detailed fix by platform

gcloud

  1. gcloud services enable translate.googleapis.com --project my-project

How to diagnose

  1. Entitlements — Plan, add-ons, beta access
  2. Project — Is the API/service enabled for this project?
  3. Region — Feature available where the account is?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

1000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)10001046 — MySQL ERROR 1046 (3D000): No database selected (MySQL)10461049 — MySQL ERROR 1049 (42000): Unknown database 'x' (MySQL)10491153 — MySQL ERROR 1153 (08S01): Got a packet bigger than 'max_allowed_packet' bytes (MySQL)11533D000 — FATAL: database "x" does not exist (PostgreSQL)3D000402 — HTTP 402 Payment Required (HTTP)402403 — HTTP 403 Forbidden (HTTP)403413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413feature_n…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.