e-invoicing

HTTP status codes

The HTTP responses the Sovos API returns for Slovakia calls, and the action each one calls for. Note that HTTP 401 and SCICloudStatusCode 401 are unrelated.

Table 1. HTTP status codes
HTTP status When you see it What to do
202 Accepted Your document submission was received by Sovos. Save the documentId from the response body and poll for notifications. 202 doesn't mean the invoice was delivered or that TDD reporting succeeded.
200 OK A GET or DELETE request succeeded. Process the response body.
400 Bad Request Your request was malformed. Check the request body and headers.
401 Unauthorized Your Bearer token is missing or expired. Refresh your token and retry.
403 Forbidden Your credentials don't have permission for this operation. Check that the correct product is assigned to your organization.
404 Not Found The resource you requested doesn't exist. Check the ID in the path parameter.
409 Conflict A duplicate endpoint or trading partner was detected. Check whether the resource already exists before creating a new one. For endpoints: if SMP registration succeeded before the API returned the conflict, the endpoint may already be registered. Don't retry without checking first.
500 Internal Server Error An unexpected Sovos platform error occurred. Wait and retry. Contact Sovos support if the problem persists.
Note:

SCICloudStatusCode 401 (validation error) and HTTP 401 (unauthorized) are different things. They share a number by coincidence. The HTTP code is in the response status line; the SCICloudStatusCode is in the notification payload body.