Laigo API Status and Error Codes

To indicate successful execution or when error occur, we utilize standard HTTP codes. In the case of errors, the response will contain extra information about the error with an error code.

Laigo REST APIs return either 200 (OK) or 201 (Created) when an API request successfully runs to completion. Status codes in the 400-500 range indicate failures.

Successful API Calls

The table below shows the typical response codes supported by Laigo API.

MethodResponse codeHTTP status codePossible response
GETOK200Request succeeds
POSTSuccess201Resource created

Error API Calls

If an error occurs when calling Laigo APIs because of an issue with the client’s input (such as incorrect data), the standard error code that starts with 400 is used.

If an operation fails because of an issue with the Laigo server, an error code that starts with 500 will be returned.

In the JSON format you will find a code in the error response key that gives a description of the error that occurred.

Errors related to incorrect user inputs

Error codeHTTP status codePossible reasons
BadRequest400Wrong file type: file types allowed: png, jpg, webp, heic, tiff, pdf.
Missing input file
Too many pages in pdf
File is too big
Unauthorized401Bad token: you didn’t provide the authentication header or the token is wrong.
Forbidden403Inference is blocked: your API access has been blocked.
PlanLimitReached403Plan limit reached: you have reached your maximum number of requests.
NotFound404Wrong endpoint: provided endpoint doesn’t match any product.
Wrong version: wrong version in base URL.
   

Errors related to server

Error codeHTTP status codePossible reasons
ServerError500An unknown error occurred during the processing of your request. Either the server is overloaded or there is an error in the application.
RequestTimeout504The request takes too much time to be processed.
WHAT’S NEXT:
> Technical Limitations

Table of Contents