Reorder the courses of a program

POST /api/v1/programs/{programId}/courses/reorder

Sets the order of the courses in a program. You send the complete ordered list, not a move.

That is deliberate: a complete list describes a final state, so two calls racing each other converge instead of fighting, and validation becomes set-based — the ids you send must be exactly the ids of that program, which refuses a foreign id by construction rather than by a check somebody could forget.

Authorization

Path parameters

Request headers

Request body

{
  "orderedCourseIds": [
    "9f2c0a1e-0000-4000-8000-000000000000",
    "9f2c0a1e-0000-4000-8000-000000000001"
  ]
}

Example

curl -X POST "$COHORTE_API_BASE_URL/api/v1/programs/$PROGRAM_ID/courses/reorder" \
  -H "x-api-key: $COHORTE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H 'Content-Type: application/json' \
  -d '{"orderedCourseIds":["'"$FIRST"'","'"$SECOND"'"]}'

Response

• 200 OK — the courses, in their new order.
• 400 Bad Request — missing Idempotency-Key, invalid JSON, duplicates, an empty list, more than 500 ids, or a set that is not exactly the courses of the program.
• 401 Unauthorized — the key is missing, invalid, or no longer attached to a member.
• 403 Forbidden — the bearer is not OWNER or ADMIN, or the program is archived.
• 404 Not Found — the program is unknown or belongs to another school.

Example response

{
  "success": true,
  "data": [
    {
      "id": "3b8e2d41-7a6c-4f1e-8b25-9c0d1e2f3a4b",
      "programId": "9f2c0a1e-4b7d-4c1a-9e3f-2a6b8c0d1e2f",
      "name": "Week 1 — Your first agent",
      "slug": "week-1-your-first-agent",
      "image": "https://files.example.com/covers/week-1.png",
      "position": 1,
      "status": "active",

Agent recipe

1. Read the courses of the program.
2. Reorder the ids client-side.
3. Send the whole list back. Never send a subset — a missing id is a rejected request, not a course left in place.

Related

• List the courses of a program
• Reorder the lessons of a program

With Idempotency-Key, retries of the identical target and payload do not write another mutation, audit or event. A different intention under that key returns 409. Results describe the currently authorized resource state.