Common Errors in DCKAP Integrator and What They Mean

When using DCKAP Integrator, you might come across error messages while syncing data between systems.

These errors generally fall into three categories:

Client Errors (4xx), Server Errors (5xx), and Success Responses (2xx).

1. Client Error Responses (4xx)

These indicate a problem with the request sent from the client (you) to the server.

• 400 – Bad Request
  The request sent is invalid or cannot be understood.
  Common causes: Incorrect API syntax, invalid parameters, or wrongly formatted data.

• 401 – Unauthorized
  The system requires valid authentication.
  Common causes: Missing or incorrect API key/token.

• 403 – Forbidden
  You don’t have permission to access this resource.
  Common causes: User role restrictions or permission settings.

• 404 – Not Found
  The resource you are trying to access doesn’t exist.
  Common causes: Deleted, moved, or incorrect resource URL.

• 415 – Unsupported Media Type
  The server refuses to accept the request because the payload format is unsupported.
  Common causes: Sending data in a format the API doesn’t accept (e.g., sending XML when only JSON is supported). Check the Content-Type header in the request.

• 429 – Too Many Requests
  You have exceeded the allowed number of requests in a given time frame.
  Common causes: API rate limits reached during heavy sync activity.

2. Server Error Responses (5xx)

These indicate an issue on the server side.

• 500 – Internal Server Error
  A generic error from the server.
  Common causes: Temporary glitches, misconfigurations, or unexpected conditions in processing.

• 502 – Bad Gateway
  The server received an invalid response from another server it relied on.
  Common causes: Connectivity issues between services.

• 503 – Service Unavailable
  The server is temporarily unable to handle requests.
  Common causes: Maintenance mode or high server load.

• 504 – Gateway Timeout
  The server did not receive a timely response from another server.
  Common causes: Delays in connected systems or large data requests.

3. Success Responses (2xx)

These indicate the request was processed successfully.

• 200 – OK
  Request completed successfully.

• 201 – Created
  A new resource has been successfully created.

• 204 – No Content
  Request completed, but no data to return (common in delete operations).

Quick Troubleshooting Tips

• Double-check API credentials before running syncs.
• Verify request parameters and data format.
• Review detailed logs in DCKAP Integrator for detailed insights.
• Monitor server or system performance during frequent 5xx errors.