# feature_not_enabled — Shorty API error

> Feature not enabled (HTTP 403): when the Shorty API returns the feature_not_enabled error, why, and how to fix it.

| Code | HTTP status | Type URI |
| --- | --- | --- |
| `feature_not_enabled` | 403 | `https://aishorty.com/docs/api/errors/feature_not_enabled` |

## When it happens

Your account or plan does not have this capability turned on. Distinct from a scope problem — the key is allowed, the plan is not.

## Example response

```json
{
  "type": "https://aishorty.com/docs/api/errors/feature_not_enabled",
  "title": "Feature not enabled",
  "status": 403,
  "detail": "This subtitle style requires Shorty Premium.",
  "instance": "urn:request:req_01J9Z8ABCDEFGH0123456789",
  "code": "feature_not_enabled",
  "request_id": "req_01J9Z8ABCDEFGH0123456789"
}
```

## How to fix it

Upgrade the plan that unlocks the feature, or contact support if you believe it should already be enabled.

## Related errors

- [insufficient_scope](/docs/api/errors/insufficient_scope) — Insufficient scope (HTTP 403)
- [quota_exhausted](/docs/api/errors/quota_exhausted) — Quota exhausted (HTTP 429)