API Errors
Woolf’s Airlock API uses structured error handling to help you detect and resolve issues during integration. Errors are returned in two forms: network errors and GraphQL errors.
Understanding API Errors
Network errors return no data and result in standard HTTP error status codes like:
400,401,413,429,500,504.GraphQL errors appear inside the response and may return partial data in a query, but mutations will not execute.
⚠️ A 401 Unauthorized response usually means your College Token is invalid, expired, or lacks required permissions.
System Error Codes
The following table lists the most common system-level API error codes and their descriptions:
Code | Message | Field |
|---|---|---|
| We are unable to access the provided URL. |
|
| Ensure the user is added to your college using their email. | – |
| Ensure the student is added to your college. | – |
| Ensure the teacher is added to your college. | – |
| Verify that the degree exists in your college. | – |
| The requested resource does not exist or is not accessible. | – |
| A grade weight is not defined for this resource. |
|
| Your college must be verified before using this API operation. | – |
| This degree is not verified and cannot be used yet. | – |
| This student has not yet completed a program. |
|
| This resource ID is already in use within your college. | – |
| The specified activity ID does not exist. | – |
| This activity cannot be modified. | – |
| Grades must be between 0 and 100. | – |
| You must provide either an activity ID or a resource + student ID. | – |
| This student cannot be created or has an invalid status. | – |
| Asset is missing import URL or content type. | – |
| A student with this email or ID already exists. | – |