---
title: "Enable a User"
method: POST
path: "/v2/users/{userId}/enable"
tags: ["Users"]
---

# Enable a User

`POST /v2/users/{userId}/enable`

If a user has been disabled this endpoints will enable them

The invoker must have the appropriate permission

A user cannot enable themself

If the user is a payor user and the payor is disabled this operation is not allowed

If enabling a payor user would breach the limit for master admin payor users the request will be rejected

## Path parameters

- `userId` string, uuid, required

## Response `204`

Success the user was enabled or was already enabled

## Other responses

- `400` — Invalid request. See Error message payload for details of failure
- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions
- `404` — The resource was not found or is no longer available

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/versions/05c3f09fc50a/schema)