# Method not allowed

> method-not-allowed: HTTP 405. Use a method named in the Allow header; every path starts /v1 and /v1/openapi.json lists them.

Source: https://emailmovers.com/mydatahub/docs/errors/method-not-allowed

`method-not-allowed` is returned with HTTP status 405. Its type URI is `https://emailmovers.com/mydatahub/docs/errors/method-not-allowed`.

## What it means

The path exists, but not for the HTTP method you used. The Allow header names the methods that work there, as RFC 9110 asks. Nothing was charged.

## What to do

Use a method named in the Allow header; every path starts /v1 and /v1/openapi.json lists them.

## Example

```json
{
  "type": "https://emailmovers.com/mydatahub/docs/errors/method-not-allowed",
  "title": "Method not allowed",
  "status": 405,
  "code": "method-not-allowed",
  "detail": "POST is not available at /v1/plans; GET is.",
  "next_step": "Use a method named in the Allow header; every path starts /v1 and /v1/openapi.json lists them."
}
```

## See also

- [REST reference](https://emailmovers.com/mydatahub/docs/reference/rest.md)

All problem types are listed on [Errors](https://emailmovers.com/mydatahub/docs/errors.md).