Sending invoice for recognition

To extract information from a scanned or photographed invoice, send a POST request to the https://api.aspose.cloud/v5.0/ocr/RecognizeAndParseInvoice Aspose.OCR Cloud REST API endpoint. To authorize the request, pass the access token in Authorization header (Bearer authentication).

The invoice and recognition parameters are provided in JSON format in the request body.

{
  "image": "Base64 string",
  "settings": {
    "language": "English",
    "makeSkewCorrect": true,
    "rotate": 0,
    "makeBinarization": false,
    "makeUpsampling": false,
    "makeSpellCheck": false,
  }
}

Providing invoice image

Photo or scan of the invoice is provided in a value of image property as a Base64 encoded string.

Recognition settings

Property Type Default value Description
language string English Specify a language for recognition.
makeSkewCorrect boolean true Automatically correct invoice image tilt (deskew) before proceeding to recognition.
Automatic deskew works for images rotated 15 degrees or less. If the scan or photo is rotated by a larger degree or upside down, you must manually specify the rotation angle.
rotate integer 0 Rotate an invoice image by the specified degree.
Should be used when the image is rotated by a significant angle or turned upside down.
makeBinarization boolean false Automatically convert an invoice to black and white before proceeding to recognition.
makeUpsampling boolean false Intellectually upscale an invoice image to improve small font recognition and detection of dense lines.
makeSpellCheck boolean false Automatically replace commonly misspelled words in recognition results with the correct ones. The dictionary is based on the selected recognition language.

Image preprocessing order

If image preprocessing filters are enabled, they are applied one after the other in the following order:

  1. Upsampling ("makeUpsampling": true)
  2. Skew correction ("makeSkewCorrect": true)

If you want to apply preprocessing filters in another order, disable the corresponding recognition settings and use self-managed preprocessing.

Return value

If successful, this method returns a string with a unique identifier (GUID) of the invoice recognition request in the queue.

Otherwise, it returns a HTTP status code corresponding to the error.

What’s next

Recognition and processing will take a few seconds, depending on the size of the source file and the current Aspose.Cloud load. See the article Fetching invoice processing result for information on how to get a JSON with parsed invoice data from the server.

cURL example