LMS Connector Errors

This guide covers error codes returned by the StackOne API and common LMS provider-specific issues.

HTTP Error Codes

All StackOne API errors follow a consistent response format:

{
  "statusCode": 400,
  "message": "Human-readable error message",
  "timestamp": "2024-01-15T10:30:00.000Z",
  "errorCode": "ValidationError",
  "provider_errors": []
}

Error Code Reference

Code	Name	Description
400	Bad Request	Invalid request parameters or malformed request body
401	Unauthorized	Missing or invalid API key, or expired credentials
403	Forbidden	Valid credentials but insufficient permissions
404	Not Found	Resource does not exist or was deleted
408	Request Timeout	Request took too long to complete
409	Conflict	Request conflicts with current resource state
412	Precondition Failed	Linked account belongs to a disabled integration
422	Unprocessable Entity	Request validation failed
429	Too Many Requests	Rate limit exceeded
500	Internal Server Error	Unexpected server error
501	Not Implemented	Feature not supported for this provider
502	Bad Gateway	Error from upstream provider

LMS Provider-Specific Issues

SAP SuccessFactors

For OCN (Open Content Network) integrations, use the /unified/lms/content/batch endpoint due to a rate limit of 1 request per 5 minutes.

The content_id field is not required for completion creation.

Debugging Tips

Check Request Logs: View detailed request/response logs in Dashboard → Logs
Inspect provider_errors: The raw provider response is included for 4xx/5xx errors
Use the Playground: Test actions interactively to isolate issues
Verify Permissions: Many 403 errors are due to missing provider-side permissions

Request Logs

View and debug API requests in the dashboard

LXP/LMS Content Aggregators External Link Approach for Learning Content Providers

​HTTP Error Codes

​LMS Provider-Specific Issues

​SAP SuccessFactors

​Debugging Tips

Request Logs

HTTP Error Codes

LMS Provider-Specific Issues

SAP SuccessFactors

Debugging Tips