Retrieve a path session: Migration guide
This guide details how the Retrieve a path session endpoint has changed (previously known as getPathSession in v1).
Key changes
- Endpoint structure: The v2 endpoint now requires both the
pathIdandsessionIdas path parameters, whereas v1 only required thesession_id.- Data separation: API v2 adopts a more modular design, distributing data previously consolidated in the v1 session response (e.g., path-specific details, tags, enrollment lists) across dedicated endpoints.
Documentation links
Here are the links to the API reference for:
Endpoint mapping
Here's the direct correlation between the v1 and v2 endpoint URLs:
- API v1:
/api/v1/paths/sessions/:session_id - API v2:
/api/v2/paths/{pathId}/sessions/{sessionId}
Behavior changes
This endpoint in API v2 reflects a refined separation of concerns. While API v1's getPathSession endpoint provided a broader set of related data (e.g., path details, skills, enrollments), API v2 distributes this information across more specialized endpoints. Consequently, to retrieve full details that were previously consolidated, you may now need to make additional calls to dedicated endpoints such as Retrieve a path, List all tags in a path, or Retrieve a path session audience.
Additionally, API v2 new capabilities and management options for open access and automatic reenrollment are reflected in new output properties like registrationRequestValidation, userLimit, and automaticReenrollment.
Input changes
This section details the specific alterations to the input requirements between API versions.
API v1 input example
curl --location 'https://app.360learning.com/api/v1/paths/sessions/685428d5df21c4596efefe74?company={{company}}&apiKey={{apiKey}}'API v2 input example
curl --request GET \
--url https://app.360learning.com/api/v2/paths/6854284dde395b87af7657c6/sessions/685428d5df21c4596efefe74 \
--header '360-api-version: v2.0' \
--header 'accept: application/json' \
--header 'authorization: Bearer your_access_token'Main input differences
Change type | API v1 | API v2 |
|---|---|---|
Modified |
|
|
Added |
|
Output changes
This section outlines the primary changes in the structure and content of a successful API response, reflecting API v2's enhanced separation of concerns. Key alterations include the renaming and restructuring of several session-related properties, the removal of path-specific details previously embedded within the session response, and the absence of direct enrollment information (e.g., enrolled groups), which was present in v1. New fields for audience management and instructor assignment have also been introduced.
API v1 output example
{
"sessionName": "July Session",
"sessionId": "685428d5df21c4596efefe74",
"sessionOwnerGroup": "6470744ad045da027bccafd1",
"sessionCreatedAt": "2025-06-19T15:12:21.000Z",
"sessionModifiedAt": "2025-06-19T15:15:45.925Z",
"instructorsMails": [
"[email protected]",
"[email protected]"
],
"startDate": "2025-07-01T15:12:21.843Z",
"endDate": "2025-07-30T23:00:00.000Z",
"pathName": "Onboarding",
"pathId": "6854284dde395b87af7657c6",
"pathOwnerGroup": "66191d23150e9d3e4ad6f60c",
"pathModifiedAt": "2025-06-19T15:14:10.532Z",
"authorsMail": [
"[email protected]"
],
"sessionAdditionalInformation": "Onboarding session for managers",
"description": "",
"skills": [],
"tags": [],
"sourceLang": "en",
"linear": true,
"certificateOutlineId": "64ff30ee0991ed01788d589d",
"steps": [
{
"_id": "65bd1aac1cb5834f304dafd1",
"type": "course"
}
],
"enrolledGroups": [],
"translationsLangs": [
{
"lang": "fr",
"published": true,
"translators": []
}
]
}API v2 output example
{
"_id": "685428d5df21c4596efefe74",
"createdAt": "2025-06-19T15:12:21.000Z",
"groupId": "6470744ad045da027bccafd1",
"instructorIds": [
"661931c78f73ada0af967859"
],
"isAudienceBuilder": true,
"mainInstructorId": "6470744ad045da027bccafd0",
"modifiedAt": "2025-06-19T15:15:45.925Z",
"name": "July Session",
"pathId": "6854284dde395b87af7657c6",
"registrationRequestValidation": "instructors",
"startDate": "2025-07-01T15:12:21.843Z",
"additionalInformation": "Onboarding session for managers",
"automaticReenrollment": {
"type": "certificationExpiryDate",
"delayDays": 30
},
"endDate": "2025-07-30T23:00:00.000Z",
"userLimit": 30,
"translations": [
{
"lang": "fr",
"published": true,
"translatorIds": [],
"translatedFields": {
"name": "Juillet"
}
}
]
}Main output differences
This section outlines the primary changes in the structure and content of a successful API response. Key alterations include the renaming and restructuring of several session-related properties, the removal of path-specific details previously embedded within the session response, and the absence of direct enrollment information (e.g., enrolled groups), which was present in v1. New fields for audience management and instructor assignment have also been introduced.
Change type | API v1 | API v2 |
|---|---|---|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
|
|
Removed |
| |
Modified |
|
|
Modified |
|
|
Modified |
|
|
Modified |
|
|
Modified |
|
|
Modified |
|
|
Modified |
|
|
Added |
| |
Added |
| |
Added |
| |
Added |
| |
Added |
| |
Added |
| |
Added |
|
Updated 7 days ago
