Confirm favorites API endpoint paths (add/list/remove) — frontend and issue docs disagree

[zigzagdev]

Motivation / 目的

The frontend (world-heritage-frontend) and the API issue history for favorites (#550, #554) currently disagree on the endpoint paths, and this is blocking frontend work on the remove-favorite feature.

フロントエンド(world-heritage-frontend)とお気に入り関連Issue(#550, #554)の間で、エンドポイントのパスに食い違いがあります。この食い違いのせいで、フロントエンド側の「お気に入り解除(remove)」機能の実装が進められない状態です。

What we found / 判明していること

• Favorite Heritage API #550 (parent) and feat: implement Presentation layer for Favorite Heritage API / お気に入りAPIのPresentation層実装 #554 (Presentation layer, closed) document:
  • POST /api/v1/users/me/favorites/{heritageId} (or POST /api/v1/users/me/favorites with a body, per Favorite Heritage API #550's earlier text)
  • DELETE /api/v1/users/me/favorites/{heritageId}
  • GET /api/v1/users/me/favorites
• On 2026-08-08, the frontend was deliberately changed away from that path (commit f6ecbb9, "align favorites API client with confirmed backend spec") to:
  • POST /api/v1/favorites with body { world_heritage_id }, 201
  • GET /api/v1/favorites, returns { status, data: WorldHeritageDto[] }
  • removeFavorite was dropped entirely at that point because "endpoint not yet confirmed" (see frontend issue #504)

Since #554 was only closed today (2026-08-16) with the /api/v1/users/me/favorites/... paths, it's unclear whether:

1. The backend actually reverted/settled on /api/v1/users/me/favorites/..., and the frontend's /api/v1/favorites (from 2026-08-08) is now stale, or
2. /api/v1/favorites is still correct and Favorite Heritage API #550/feat: implement Presentation layer for Favorite Heritage API / お気に入りAPIのPresentation層実装 #554's documented paths just haven't been updated to match what's actually deployed.

Ask / お願いしたいこと

Please confirm the current, actually-deployed contract for all three favorites endpoints so the frontend can implement remove correctly:

• Add: method + path + request body shape + success status code
• List: method + path + response shape
• Remove: method + path + request body (if any) + success status code + not-found status code

Related

• Frontend: refactor: change Repository interface argument from UseCommand to UserEntity #504 (remove-favorite feature, blocked on this)
• API: Favorite Heritage API #550 (parent), feat: implement Domain layer for Favorite Heritage API / お気に入りAPIのDomain層実装 #551 (Domain), feat: implement Presentation layer for Favorite Heritage API / お気に入りAPIのPresentation層実装 #554 (Presentation)