# mutations_not_enabled

Source: https://capacms.com/docs/errors/mutations_not_enabled

405 method. The request tried to write.

| HTTP status | `type`   | Surfaces      |
| ----------- | -------- | ------------- |
| 405         | `method` | REST, GraphQL |

## What it means

The request tried to write. `/api/` reads only for now, and Capa's GraphQL API reads only.

| When                         | What the `hint` tells you                   |
| ---------------------------- | ------------------------------------------- |
| a POST, PUT, PATCH or DELETE | no hint on REST: writes are not enabled yet |

## What to do

Send a GET, or a GraphQL query rather than a mutation. Content is edited in the Capa admin, or through the session routes for scheduling, webhooks and workspaces.

## The response

HTTP 405:

```json
{
  "error": {
    "type": "method",
    "code": "mutations_not_enabled",
    "message": "Writes are not enabled on /api/ yet.",
    "docs": "https://docs.capacms.com/errors/mutations_not_enabled"
  },
  "meta": {
    "version": "2026-10-01",
    "contract": 1,
    "requestId": "req_0f3c…"
  }
}
```

## On GraphQL

`/api/graphql` answers the same `code` inside `errors[].extensions`. The status depends on the `Accept` header you send ([status codes](https://capacms.com/docs/api/graphql#status-codes)):

| `application/json` | `graphql-response+json` | When                                                                                                                                                            |
| ------------------ | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 405                | 405                     | a `mutation` operation anywhere in the document, whichever operation `operationName` picks. The `Allow` header names the methods the route answers, `GET, POST` |

## See also

* [API reference](https://capacms.com/docs/api)