# GET /api/v1/wordpress/users

> List, create or re-role WordPress users

- Group: applications
- Tier: R
- Required scope: read:hosting
- Docs: https://api.inleed.com/reference/applications/manage-wordpress-users

## Description

`action=list` returns `users[]` `{id, login, displayName, email, roles}` and needs only read access. `create` needs `login`, `email` and `role` (optional `display_name`) and returns the generated password once in `user.password`; `set_role` needs `id` and `role`. Both require `write:hosting`.

## Query parameters

- `input` — string (required). A domain, email address, website URL, or Inleed service id — for example example.se, info@example.se or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.

## Request

```bash
curl -X GET "https://mcp.inleed.com/api/v1/wordpress/users?input=example.se" \
  -H "Authorization: Bearer inl_live_…"
```

## Errors

- **400**  — codes: invalid_request
- **401** No token was presented, or the token is revoked, expired or unknown. — codes: unauthorized, token_expired, token_revoked
- **403** The token lacks a required scope, or this account does not own the resource. — codes: insufficient_scope, domain_not_owned
- **404** No such resource for this account. — codes: not_found
- **422** Validation error — codes: validation_failed
- **429** The rate limit for this token is exhausted. See `Retry-After`. — codes: rate_limited
- **500** Something went wrong on our side. The failure is logged against `requestId`. — codes: internal_error

## Related

- POST /api/v1/wordpress/users — https://api.inleed.com/reference/applications/create-wordpress-users
- PATCH /api/v1/wordpress/users — https://api.inleed.com/reference/applications/update-wordpress-users