Skip to main content

Error Handling

Sample Error Responses

Written by Lenka Haringerová

Users are informed about errors via the HTTP status code.

HTTP Code

Meaning

200 OK

The operation was completed successfully.

201 Created

The record was created successfully. The Location header contains the URL of the newly created record, and the response body also includes the identifier.

304 Not Modified

The record was not modified (used in combination with the If-Modified-Since header).

400 Bad Request

Bad request. This typically occurs during a PUT operation that has failed (e.g., you are referencing an object that does not exist).

401 Unauthorized

The user must log in to perform the requested operation.

402 Payment Required

The target system does not have the REST API for write operations activated. For read operations, a 404 is returned instead.

403 Forbidden

The user does not have permission to perform this operation. This error is also displayed if the operation is not permitted by the license.

404 Not Found

Record not found. This may refer to a register or a specific record (e.g., because it has been deleted).

405 Method Not Allowed

A disallowed method was used. For example, using the POST method where data can only be read using the GET method.

406 Not Acceptable

The target format is not supported for the specific resource (e.g., exporting an address book as ISDOC).

500 Internal Server Error

An internal server error occurred while processing the request. This should not happen under normal circumstances and always indicates a bug in the ABRA Flexi code. Please notify us.

Unless the error is a 500, the response typically also includes a description in a machine-readable format (XML, JSON). The format is identical to validation messages.

Example error response:

<?xml version="1.0"?> 
<winstrom version="1.0">
<success>false</success>
<result>
<id>105</id>
<error>Je očekáváno číselné ID, ale 'null' není číslo</error>
</result>
</winstrom>
Did this answer your question?