Currently, the GET /api/v1/courses/:course_id/content_migrations/:id endpoint does not return the date_shift_options field in the settings object, even though it can be specified when creating or updating a content migration via POST and PUT. This is problematic because developers and integrations may need to know whether the "Adjust events and due dates" option was selected during a course import. For example, in our use case, we are developing logic that depends on whether the dates were shifted. Since the GET call doesn't return this information, we cannot verify user actions, audit settings, or make decisions based on this key parameter. Instructure support has confirmed that this is the expected behavior and that this field is only visible to site admins. However, this restriction breaks consistency in the API and limits functionality for users with valid permissions at the course level.
We propose that the GET Content Migrations API endpoint should return the date_shift_options field in the settings object. This would align the behavior of the API with the POST and PUT endpoints, which already allow sending this data. It’s inconsistent and counterintuitive to allow updating a value that cannot be read afterward. Making date_shift_options visible in the GET response would improve API transparency, support auditing, and enable smarter integrations around content imports.
