Transfer an enrollment

POST /api/v1/enrollments/{enrollmentId}/transfer

Moves one participation to another cohort of the same program. The enrollment itself does not change: history, progress, deliverables, reviews, attendance, current action, deadlines and the assigned coach all stay attached to it. Only the cohort context changes, on the date you choose — which is what live sessions, the community space and cohort dashboards read from that moment on.

Authorization

Organization role

Business authorization

Moving someone to another promotion is an operating decision, so it takes the same authorization as pausing one: a coach assigned to the enrollment can document sessions and plan interventions, but cannot transfer. A platform-wide role grants nothing here. An enrollment or a cohort of another organization is refused without revealing whether it exists.

Path parameters

Request headers

Request body

A cohort is a valid target when all three hold:

• it belongs to the same program as the enrollment;
• it still accepts an entry — a completed or archived cohort does not;
• it is not the cohort the enrollment is already in.

A cohort still in preparation is a valid target. Its content stays locked for the member until that cohort opens, exactly as it would for a new enrollment.

{
  "toCohortId": "3b0e51a4-0000-4000-8000-000000000000",
  "effectiveAt": "2026-09-01T09:00:00.000Z",
  "reason": "Resumes with the next promotion."
}

Example

curl -X POST "$COHORTE_API_BASE_URL/api/v1/enrollments/ENROLLMENT_ID/transfer" \
  -H "x-api-key: $COHORTE_API_KEY" \
  -H "Idempotency-Key: transfer-2026-09-01" \
  -H 'Content-Type: application/json' \
  -d '{"toCohortId":"COHORT_ID","reason":"Resumes with the next promotion."}'

Response

• 201 Created — the participation now belongs to the target cohort.
• 200 OK — the same Idempotency-Key replayed the original transfer; nothing was written a second time.
• 400 Bad Request — missing Idempotency-Key, invalid JSON, an empty reason, or an effective date in the future.
• 401 Unauthorized — the key is missing, invalid, or no longer attached to a member.
• 403 Forbidden — the bearer cannot change the lifecycle of enrollments in this organization.
• 404 Not Found — the enrollment or the target cohort is unknown, or belongs to another organization.
• 409 Conflict — the participation is closed, the target cohort belongs to another program, no longer accepts an entry, or is the one the enrollment is already in.

Response fields

Example response

{
  "success": true,
  "replayed": false,
  "data": {
    "id": "7c1d9a20-0000-4000-8000-000000000000",
    "enrollmentId": "4af4cd8d-0000-4000-8000-000000000000",
    "fromCohortId": "0f2a77b1-0000-4000-8000-000000000000",
    "fromCohortName": "Autumn promotion",
    "toCohortId": "3b0e51a4-0000-4000-8000-000000000000",
    "toCohortName": "Summer 2026 promotion",
    "effectiveAt": "2026-09-01T09:00:00.000Z",
    "reason": "Resumes with the next promotion.",
    "transferredBy": "6d41ab55-0000-4000-8000-000000000000",
    "transferredByName": "Paul Vidal",
    "createdAt": "2026-09-01T09:00:05.000Z"
  },
  "correlationId": "0f6b1d92-0000-4000-8000-000000000000"
}

Agent recipe

1. List the cohorts of the enrollment's program and keep those that still accept an entry, excluding the one the member is already in.
2. Transfer with a reason your team will read later, and an effective date if the move was agreed earlier.
3. Read the enrollment timeline to confirm the move — it now carries a "transferred" entry naming both cohorts.

Notes

• A paused participation can be transferred, and that is the main use case: someone who interrupted their journey resumes with the next promotion. Only a closed participation is refused. The transfer does not resume a pause — that is a separate call.
• Capacity is not checked. There is no headcount or seat limit anywhere in the product yet, so a target cohort is never refused for being full. If your process caps a promotion, enforce it before calling.
• No notification, email or message is sent by this endpoint, to the member or to anyone else.
• The coach assignment, deadlines, current action, open blockers, planned interventions and recorded attendance are untouched. Attendance already recorded on a session of the previous cohort stays: it belongs to the participation, not to the cohort.
• What follows the member immediately, because it is read from the current cohort: visible live sessions, the cohort community space, the content lock that depends on the cohort state, and the cohort dashboards. The enrollment appears in the target cohort's views with its full history and leaves the previous one.
• Retrying with the same Idempotency-Key returns the original transfer and writes no second record, audit entry or event.
• One enrollment can be transferred as many times as needed, including back to a cohort it already left. Each move is recorded with its own effective date, so the whole path stays readable.
• The transfer, its audit entry and its domain event are written in one transaction.

Related

• Pause an enrollment
• Resume an enrollment
• Close an enrollment
• Read an enrollment timeline