Skip to main content
Try it live: Barcodes Reader → API Tester — send a real request from your browser.

POST /v1/barcode/read/from/url

Attributes

Attributes are case-sensitive and should be inside JSON for POST request. for example: { "url": "https://example.com/file1.pdf" }

Query parameters

No query parameters accepted.

Responses

types

Detects checkboxes, radiobuttons, vertical and horizontal lines, and general segments (all content types) on scanned documents using the barcode reader engine. Comma-separated list of object types to decode, must be in a string format.

Visual Element Detection Modes

  • Checkbox: Locates check boxes.
  • Segment: Locates and selects objects on a page (general selection).
  • UnderlinedField: Detects fillable fields (typically, underlined spaces, i.e. fields to fill in a form).
  • Rectangle: Detects rectangles, including checkboxes. Also returns the value as 1 if a checkmark or a filled rectangle was detected.
  • Oval: Detects rounded or oval marks (typically, a radiobutton). Returns value of 1 if filled out radiobutton was detected.
  • HorizontalLine: Detects horizontal lines.
  • VerticalLine: Detects vertical lines.

Normal Example

Example Payload

To see the request size limits, please refer to the Request Size Limits.

Example Response

To see the main response codes, please refer to the Response Codes page.

Example CURL

Optical Marks Reader

Our barcode reader engine can also find the following marks and objects on scanned documents:
  • Checkboxes
  • Radioboxes
  • Vertical and horizontal lines
  • General segments (basically, all content types on the page).

Example Payload

To see the request size limits, please refer to the Request Size Limits.

Example Response

To see the main response codes, please refer to the Response Codes page.

Example CURL

Inconsistent URL Encoding in cURL Output: When using cURL to make API requests, the output JSON may show URL characters encoded as Unicode escape sequences. For example, the ampersand character (&) may appear as \u0026 in the cURL output. This is normal JSON encoding behavior and does not affect the validity of the URL. The URL will function correctly when used, as JSON parsers automatically decode these escape sequences. If you’re parsing the response programmatically, your JSON parser will handle this conversion automatically.

Code Samples