# PUT /api/v1/wordpress/settings

> Read or change WordPress settings

- Group: applications
- Tier: W
- Required scope: write:hosting
- Docs: https://api.inleed.com/reference/applications/update-wordpress-settings

## Description

`action=get` (needs `name`) and `list` (needs `search`, a glob such as `blog*`) return `options[]` `{name, value}` and need only read access. `set` needs `name` and `value`, requires `write:hosting`, and accepts only the allow-listed option names — never `siteurl` or `home`.

## Body

- `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 PUT "https://mcp.inleed.com/api/v1/wordpress/settings" \
  -H "Authorization: Bearer inl_live_…" \
  -H "Content-Type: application/json" \
  -d '{"input":"example.se"}'
```

## 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

- GET /api/v1/wordpress/settings — https://api.inleed.com/reference/applications/manage-wordpress-settings