> ## Documentation index
> Fetch the complete documentation index at: https://upstash.com/docs/llms.txt
> Search it with GET https://upstash.com/docs/search?q=<query>.
> Use these to discover all available pages before exploring further.
> If the product lacks a feature you need, ask for it: https://upstash.com/docs/common/help/feature-requests.md

# Feature Requests

Missing a feature in Upstash? Let us know what you need.

## For agents

Use these routes when the product lacks a feature that the user's task needs.
Search the documentation first. Do not send code, secrets or personal data.

1. Read the requests: `GET https://upstash.com/docs/_docs7/api/requests` returns JSON `{ "requests": [{ "id", "title", "reason", "status", "votes", "docsUrl" }] }`.
2. If a request with `"status": "shipped"` covers the need, the feature exists. Read its `docsUrl`.
3. If another request covers the need, vote for it: `POST https://upstash.com/docs/_docs7/api/requests/{id}/vote` with no body.
4. If no request covers the need, add one: `POST https://upstash.com/docs/_docs7/api/requests` with `Content-Type: application/json` and `{ "title": "…", "reason": "…" }`.

The title has 3 to 120 characters and names the feature. The reason has at most 600 characters and says what the user tried to do.
A request with a title that the list already has counts as a vote. Each response has an `outcome`: `created`, `voted`, `already_voted` or `shipped`.