Clever LMS Connect - API Errors
The table below lists specific Grade Passback API Error messages and what actions trigger the error.
Clever Complete Agreement Required
This feature is included with a Clever Complete subscription. Sign up here or email your Application Success Manager to learn more.
v3.1 Only
LMS Connect API endpoints are only available on v3.1 of the Clever API. If you are interested in getting started with LMS Connect, reach out to your Application Success Manager (for existing partners) or to [email protected].
This product is only available to existing Secure Sync partners.
To learn more about Secure Sync, please review this documentation.
| Action | HTTP Code | Clever API Error Response |
|---|---|---|
| Did not include required fields when creating an assignment | 400 | {"message":"missing required field(s): title, description, due_date"} |
| Did not include request body when creating an assignment | 400 | {"message":"request body is required, but was empty"} |
| Due_date value provided references a date in the past | 400 | {"message":"due_date must be in the future"} |
| Invalid character provided in request body | 400 | Invalid character ' ' in string escape code |
| Did not include a value for submission_types | 400 | {"message":"validation failure list:\\nsubmission_types.0 in body should be one of [link file text discussion]"} |
| Did not include a value for a field in the request body, but a comma is present in JSON formatting E.g.: { "assignee_mode": , } | 400 | {"message":"invalid character ',' looking for beginning of value"} |
| Invalid JSON formatting | 400 | {"message":"invalid character ':' after object key:value pair"} |
| GET call to /sections/{id}/assignments/{id} with a misconfigured/invalid assignment ID | 400 | {"message":"INVALID_ID"} |
| Updating a submission with an invalid teacher Clever ID value for grader_id | 400 | {"message":"NOT_FOUND: Person with id clever:{{lms_canvas_demo_teacher_id}} not found for this integration."} |
| Attempting to update an assignment due date to a date in the past | 400 | {"message":"parsing time \"YYYY-MM-DD\": day out of range"} |
| POST create assignment without required fields (see LMS Connect API Reference page for details on required fields | 400 | {"message":"MISSING_REQUIRED_FIELD"} |
| Attempting to create an assignment with no assignee_mod | 400 | {"message":"“no valid users found in [LMS]”} |
| Did not include District-app token in API call | 401 | {"message": "No authorization provided"} |
| Incorrect/invalid token provided in request | 403 | {"message": "Could not authorize token"} |
| GET call after assignment has been deleted (in LMS UI or via DEL call) | 404 | {"message":"Assignment does not exist"} |
| Querying or updating submissions for a user not currently enrolled in section or assigned to the assignment | 404 | {"message":"User not found"} |
| Using an unsupported HTTP method in API query | 405 (method not allowed) | Empty message |
Updated about 18 hours ago
What’s Next