# PUT /api/v1/backups/schedule

> Report backup scheduling as not settable through the API

- Group: backups
- Tier: W
- Required scope: write:hosting
- Docs: https://api.inleed.com/reference/backups/set-backup-schedule

## Description

Returns `{supported:false, applied:false, reason:"not_available", detail}`. Backup scheduling is managed in DirectAdmin, not through this API; nothing is changed.

## Request

```bash
curl -X PUT "https://mcp.inleed.com/api/v1/backups/schedule" \
  -H "Authorization: Bearer inl_live_…"
```

## Response · 200

```json
{
  "supported": true,
  "applied": true,
  "reason": "example.se",
  "detail": "Resolved via the owning account."
}
```

## Errors

- **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
- **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/backups/schedule — https://api.inleed.com/reference/backups/get-backup-schedule
- GET /api/v1/backups — https://api.inleed.com/reference/backups/list-backups