---
title: "Update Redirect (PUT)"
method: PUT
path: "/redirects/{id}"
tags: ["Redirects"]
---

# Update Redirect (PUT)

`PUT /redirects/{id}`

Update a redirect rule using PUT. The current implementation treats PUT and PATCH identically.

## Path parameters

- `id` string, required

## Request body

- RedirectUpdateRequest
  - `jsonapi` object, required — JSON:API version metadata included in every JSON:API response.
    - `version` string, required — Implemented JSON:API version.
  - `data` object — Redirect resource payload to update.
    - `type` 'redirects', required — Resource type identifier. Always `redirects`.
    - `id` string, required — Redirect ID
    - `attributes` object — Redirect fields to update.
      - `from_path` string — Source path (optional)
      - `to_path` string — Target path (optional)
      - `redirect_type` 307 | 308 — Redirect type (optional)

## Response `200`

Redirect updated successfully

## Other responses

- `400` — Bad request
- `401` — Authentication failed
- `403` — Insufficient permissions
- `404` — Resource not found
- `409` — Resource conflict
- `500` — 서버 내부 오류

---

[API](https://skmtc.dev/inblog/apis/inblog-api.md) · [All operations](https://skmtc.dev/inblog/apis/inblog-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/inblog/inblog-api/revisions/445daf773d30/schema)