The Change Log page displays previous API and CLI changes. The heading date indicates the date that the API or CLI code was made available in the production environment.
2026-06-20
New Quizzes Data Namespace for DAP Query API & DAP CLI 2.2.0.
Announcement Date: 2026-03-16
New Quizzes Data Namespace
- New Feature: Dedicated availability of New Quizzes (NQ) data introduced as the
new_quizzes namespace in the CD2/DAP Query API datasets. - Known limitation: Data is refreshed every 8 hours for
new_quizzes namespace. - Schema Status: The data model is transformed to mirror the structure of
quizzes, quiz_questions, quiz_submissions, and quiz_groups found in the existing canvas namespace. Thus a crosswalk is provided in the documentation.
DAP CLI Update
- Version: DAP CLI version 2.2.0 is released.
- Support: DAP CLI 2.2.0 includes specific support for the new_quizzes namespace.
- Action Required: Users must update their local installation to access NQ data through the DAP CLI.
Update Command: pip install -U instructure-dap-client
2026-06-20
User-Agent Header Enforcement
Announcement Date: 2026-03-13
Beta Availability: 2025-10-01
To strengthen API security and governance, all HTTP requests must include a User-Agent header. Requests without this header are rejected in Beta as of October 1, 2025, and in Production on June 20, 2026.
Related Resource: Enforcing User-Agent Header for Canvas API Requests
2026-04-08
Announcement Date: 2026-03-27
Beta Availability: 2026-03-26
Grade Change Logs Subaccount Query Support
Allows users in a subaccount to query Grade Change logs by assignment_id or course_id. Additional parameters (grader_id, student_id) can be used to further filter results.
2026-03-09
Announcement Date: 2026-03-09
DAP Query API schema change is required immediately due to keep prevent data loss. Thus the change need to happen earlier.
submissions
A data type change for a column:
Updated column: points_deducted
Changed data type from: decimal(6,2) to: decimal(12,2)
Updated numeric bounds from:
-10,000 to 10,000 to: -10,000,000,000 to 10,000,000,000
Schema version increased from 2 → 3.
2026-04-18
Announcement Date: 2025-12-18
Beta Availability: Gradual rollout began 2025-11-01
Updated on 2026-01-05: Changed production date from 2026-02-21 to 2026-04-18.
Changed
GET Requests with a body are rejected with a 403 status code
Platform infrastructure is transitioning to utilize AWS CloudFront (CDN) for application delivery to ensure continued performance and scalability. This is a change to the underlying infrastructure that is available in Beta and Test environments and will be gradually rolled out to most accounts in Production in January 2026. In almost all cases, this requires no action from customers or vendors and is entirely transparent to users.
This update includes one known side effect that impacts a very small subset of Canvas API users:
GET requests cannot have a body. This is how AWS interprets the definition in RFC 9110 and RFC 7231 that "A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some existing implementations to reject the request." The CDN will respond with a 403 to these requests.
Any account identified as receiving GET API requests with a body, rather than using query parameters, will not be included in the January rollout. This behavior is very rare. Affected accounts will have until February 21, 2026 to update integrations accordingly, and will be notified and will be notified via notice in the Developer Keys page as well as via their CSM. Examples of the required adjustments are available in the related resource. If you don’t hear about this from your CSM or otherwise, you most likely are not affected and do not need to do anything.
Related Resource: Improving Canvas Infrastructure with a Content Delivery Network
2026-03-11
Announcement Date: 2026-03-02
Related Resource: New Tables and Schema Updates in CD2 Canvas & Canvas Logs - Instructure Community
Release Type: Schema Enhancement
Namespaces Affected: `canvas`, `canvas_logs`
Backward Compatibility: Compatible (see notes below)
New Tables (canvas namespace)
- `outcome_calculation_methods`
- `outcome_friendly_descriptions`
- `accessibility_resource_scans`
- `accessibility_issues`
- `custom_grade_statuses`
All tables include standard `created_at` and `updated_at` timestamps.
`submissions` (canvas namespace)
- Column: `points_deducted`
- Type change:
- From: `decimal(6,2)`
- To: `decimal(12,2)`
- Updated bounds:
- From: (-10,000, 10,000)
- To: (-10,000,000,000, 10,000,000,000)
🔄 Updated Tables
`web_logs` (canvas_logs namespace)
- Added enum value `ACL` to `http_method`
- Schema version bumped: **7 → 8**
⚠️ Implementation Notes
- Downstream systems enforcing strict enum validation must include `ACL`.
- Systems enforcing numeric bounds should update constraints for `points_deducted`.
- DAP CLI users do not need to take action.
2026-03-21
User-Agent Header Enforcement
This feature is currently delayed in the production environment and will be included in a future release.
Note: This update is delayed because a significant number of partner calls would continue to fail.
Announcement Date: 2026-03-13
Announcement Date: 2026-01-12
Beta Availability: 2025-10-01
To strengthen API security and governance, all HTTP requests must include a User-Agent header. Requests without this header are rejected in Beta as of October 1, 2025, and in Production on March 21, 2026.
Related Resource: Enforcing User-Agent Header for Canvas API Requests
2026-01-17 [Delayed as of 2026-01-09]
Updated: Changed Production release date from 2026-01-01 to 2026-01-17.
Announcement Date: 2025-10-09
Beta Availability: 2025-10-01
User-Agent Header Enforcement
To strengthen API security and governance, all HTTP requests must include a User-Agent header. Requests without this header are rejected in Beta as of October 1, 2025, and in Production on January 1, 2026.
Related Resource: Enforcing User-Agent Header for Canvas API Requests
