Edlink provides comprehensive logging tools to give you complete visibility into the traffic flowing between your application and school data providers. Instead of acting as a "black box," the Edlink Dashboard exposes the full lifecycle of every API request to help you debug issues quickly.
Incoming Request Logs
Every time your application makes an HTTP request to the Edlink API, we create a detailed log entry. These logs serve as the source of truth for your integration activity.
You can inspect the full context of every interaction, including:
- Request Details: The HTTP method, URL path, query parameters, and headers.
- Payloads: The exact JSON body your application sent to us.
- Responses: The status code, response body, and headers we returned to you.
- Metadata: The specific integration, user, and time duration of the request.
Outbound Request Tracing
A single request to the Edlink API often triggers multiple requests to the underlying LMS or SIS. For example, creating an assignment might require Edlink to first look up a course ID, then create the assignment object, and finally assign it to specific students.
Edlink logs every Outbound Request we make on your behalf. When viewing an Incoming Request in the dashboard, you can see a list of all associated Outbound Requests. This allows you to pinpoint exactly where a failure occurred. You can verify if an error originated from your application logic, the Edlink platform, or the upstream provider (e.g., Canvas returning a 500 Internal Server Error).
AI Error Analysis
Error messages from legacy SIS platforms or complex LMS APIs can often be cryptic or undocumented. To assist with troubleshooting, Edlink provides AI Error Analysis directly within the request log view.
When a request fails, you can use the AI analysis tool to interpret the error. The AI examines the request context, the specific provider's error code, and the response body to provide a human-readable explanation of what went wrong and actionable steps to fix it. This significantly reduces the time spent reading external API documentation or contacting support.
SSO Login Traces
In addition to API request logs, Edlink also captures detailed traces of SSO login attempts made through our platform. This is especially useful for diagnosing authentication issues that teachers and students may face when accessing their LMS via SSO.
To learn more about SSO login traces, see the associated developer guide.