Skip to content
RetorioRetorio API Docs

Change an assignment’s window

PUT
/cohorts/{id}/programs/{cohortProgramExtId}
curl --request PUT \
  --url https://api.retorio.com/be/v2/cohorts/b2d7e4a1_55c3_4f28_9e10_7a3d6c4b8f02/programs/e90f3b7c_1a26_44d5_b8c1_0d94e7f25a63 \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "startDate": "2026-12-01T00:00:00.000Z", "endDate": "2027-03-31T23:59:59.000Z" }'

Changes the startDate/endDate of an existing assignment.

Authentication

Section titled “Authentication”
Auth
Access key
Roles
Owner / Admin / Custom

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
id
required
string

Example 

b2d7e4a1_55c3_4f28_9e10_7a3d6c4b8f02
cohortProgramExtId
required
string

Example 

e90f3b7c_1a26_44d5_b8c1_0d94e7f25a63

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
startDate
required
string

Example 

2026-12-01T00:00:00.000Z
endDate
required
string
nullable

Example 

2027-03-31T23:59:59.000Z

Responses

Section titled “Responses”

200

Section titled “200”

OK

Media typeapplication/json
object
createdAt
required
string format: date-time
extId
required
string
<= 64 characters
startDate
required
string format: date-time
endDate
required
string format: date-time
nullable
order
required
integer
programId
required

The assigned program’s ext id.

string
title
required

The assigned program’s title.

string
scenarioStatusCounts
required
object
unpublished
required
integer
publishing
required
integer
published
required
integer
cohortProgramStatus
required

upcoming before startDate, finished once endDate has passed (never for an open-ended assignment, which has no endDate), active otherwise.

string
Allowed values: upcoming active finished

Example 

{
  "cohortProgramStatus": "upcoming"
}

400

Section titled “400”

The request body is not valid, a date is not a valid ISO date, or startDate is not before endDate. Also answered when the request body is not valid JSON.

Media typeapplication/json
Any of:
object
message
required
string
status
required

Canonical error name, e.g. INVALID_ARGUMENT.

string
details
nullable

Example generated

{
  "message": "example",
  "status": "example",
  "details": "example"
}

401

Section titled “401”

Not authenticated: the bearer token is missing, malformed, expired or revoked, its sign-in method does not match your organization’s configuration, the user it belongs to was removed, or your organization is deactivated.

Media typeapplication/json
object
message
required
string
status
required

Canonical error name, e.g. INVALID_ARGUMENT.

string
details
nullable

Example generated

{
  "message": "example",
  "status": "example",
  "details": "example"
}

403

Section titled “403”

Refused: the token does not belong to an admin, or your organization does not have the coaching product, or the admin’s roles do not grant cohorts:manage.

Media typeapplication/json
Any of:
object
message
required
string
status
required

Canonical error name, e.g. INVALID_ARGUMENT.

string
details
nullable

Example generated

{
  "message": "example",
  "status": "example",
  "details": "example"
}

404

Section titled “404”

No cohort with this id in your organization, or no assignment with this ext id in it.

Media typeapplication/json
object
message
required
string
status
required

Canonical error name, e.g. INVALID_ARGUMENT.

string
details
nullable

Example generated

{
  "message": "example",
  "status": "example",
  "details": "example"
}

413

Section titled “413”

The request body is larger than 10 MB.

Media typeapplication/json
object
statusCode
required
integer
message
required
string
error
required

The HTTP reason phrase, e.g. Bad Request.

string

Example generated

{
  "statusCode": 1,
  "message": "example",
  "error": "example"
}

415

Section titled “415”

The Content-Type charset or the Content-Encoding is one the API cannot decode. Send UTF-8 JSON without a content encoding.

Media typeapplication/json
object
statusCode
required
integer
message
required
string
error
required

The HTTP reason phrase, e.g. Bad Request.

string

Example generated

{
  "statusCode": 1,
  "message": "example",
  "error": "example"
}

500

Section titled “500”

Internal Server Error

Media typeapplication/json
object
key
additional properties
nullable

Example generated

{
  "additionalProperty": "example"
}

Retorio is GDPR and DSGVO compliant, EU AI Act aligned, ISO 27001 certified, and hosted on Google Cloud with EU data residency. For anything specific to your rollout, ask your Retorio contact.