Skip to main content
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": []
}
CodeNameDescription
400Bad RequestInvalid request parameters or malformed request body
401UnauthorizedMissing or invalid API key, or expired credentials
403ForbiddenValid credentials but insufficient permissions
404Not FoundResource does not exist or was deleted
408Request TimeoutRequest took too long to complete
409ConflictRequest conflicts with current resource state
412Precondition FailedLinked account belongs to a disabled integration
422Unprocessable EntityRequest validation failed
429Too Many RequestsRate limit exceeded
500Internal Server ErrorUnexpected server error
501Not ImplementedFeature not supported for this provider
502Bad GatewayError 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

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

Request Logs

View and debug API requests in the dashboard