# OAuth scope not supported or not offered

> The oauth.invalid_scope error (400) means a requested or granted OAuth scope is not supported or not offered. See which scopes exist and how to fix the request.

## Error code

```json
{
  "code": "oauth.invalid_scope",
  "docUrl": "https://doc.mor.payments.ai/errors/oauth-invalid-scope"
}
```

## HTTP status

400

## Cause

One of two things:

- The `scope` sent to `/v1/oauth/device_authorization` names a scope Payments AI does not support, or lists no supported scope at all. The OAuth endpoints answer this as an RFC 6749 body, `{ "error": "invalid_scope", "error_description": "..." }`, and the description names the rejected scope.
- The approval page was confirmed with no scope ticked, or with a scope the device did not ask for. Only scopes from the offered list can be granted.

## How to fix

Send only scopes from the scope table in the [agent auth guide](https://doc.mor.payments.ai/auth.md), separated by spaces, or leave `scope` out so the person approving can pick from every supported scope. On the approval page, tick at least one of the offered scopes.

## Related

- [Connect without a terminal](/connect#connect-without-a-terminal)
