---
title: "Upsert the peer leader's Medley feedback responses (AC9/10)"
method: PUT
path: "/api/participant/sessions/{sessionId}/post-session/leader-feedback"
tags: ["Peer Leader Post-Session"]
---

# Upsert the peer leader's Medley feedback responses (AC9/10)

`PUT /api/participant/sessions/{sessionId}/post-session/leader-feedback`

## Request

- Base URL: `https://api.production.yourmedley.com`
- URL: `https://api.production.yourmedley.com/api/participant/sessions/{sessionId}/post-session/leader-feedback`
- Auth: none declared

NOTE the `leader-feedback` sub-path. The participant E3.4 post-session
routes (MED-806) are mounted on the same `/participant/sessions` prefix
and own `/post-session/feedback`; the peer leader's two-section form is a
distinct surface persisting to `peer_leader_session_feedback`, so it uses
a disambiguated path to avoid the Express route collision.

## Path parameters

- `sessionId` string, uuid, required

## Request body

- object
  - `responses` object, required

## Response `200`

Feedback persisted

## Other responses

- `400`: Validation error
- `401`: Unauthorized
- `403`: Caller is not the peer leader for this session
- `500`: Server error

---

[API](https://skmtc.dev/withmedley/apis/medley-api.md) - [All operations](https://skmtc.dev/withmedley/apis/medley-api/llms.txt) - [OpenAPI document](https://skmtc.dev/withmedley/apis/medley-api/revisions/40aaac5ca6bd?raw)