POST /api/v2/account/setSessions
Adds one or more sessions to a participant's personal schedule (My Schedule) for a given event.
Authentication
Authorization: Bearer <your_api_key>
Endpoint
POST /api/v2/account/setSessions
Body Parameters
Content-Type: multipart/form-data
|
Parameter |
Type |
Required |
Accepted Values / Format |
Description |
|---|---|---|---|---|
|
|
integer |
Yes |
Valid account ID |
The internal ID of the participant whose schedule is being updated |
|
|
integer |
Yes |
Valid event ID |
The event the sessions belong to |
|
|
string |
Yes |
Comma-separated session IDs (e.g. |
One or more session IDs to add to the participant's schedule |
Response
Success (HTTP 200)
{
"code": 200,
"data": {
"id": 12345,
"status": "Session with ID 10,11 was added to account 12345 succesfully"
},
"response_id": "1700000000.12345"
}
|
Field |
Type |
Description |
|---|---|---|
|
|
integer |
The account ID |
|
|
string |
Human-readable summary of the result |
|
|
array |
Present only when individual session additions failed. Lists per-session error messages |
No valid sessions to add
{
"code": 200,
"data": {
"id": 12345,
"status": "No valid session ID to add"
}
}
Per-session errors (non-fatal)
If a session ID in the list is invalid or already in the participant's schedule, that specific session will be skipped and reported in the errors array. Other valid sessions in the same request are still added.
Error Responses
|
HTTP Code |
Condition |
Error Message |
|---|---|---|
|
400 |
|
|
|
400 |
|
|
|
400 |
Account not found |
|
|
400 |
Event not found |
|
|
403 |
Missing or invalid API key |
|
Example Request
curl -X POST "https://your-event-domain.com/api/v2/account/setSessions" \
-H "Authorization: Bearer your_api_key_here" \
-F "id=12345" \
-F "event_id=7" \
-F "sessions=10,11,12"
Example Response
{
"code": 200,
"data": {
"id": 12345,
"status": "Session with ID 10,11,12 was added to account 12345 succesfully"
},
"response_id": "1700000000.12345"
}