Skip to main content

Overview

When extracting content with layout information, Pulse API returns bounding box coordinates for text, tables, and images. This spatial data enables precise document understanding and region-based extraction.

Bounding Box Format

Bounding boxes are returned as normalized coordinates (0-1 range) in an 8-point format:
Where:
  • (x1, y1) = Top-left corner
  • (x2, y2) = Top-right corner
  • (x3, y3) = Bottom-right corner
  • (x4, y4) = Bottom-left corner
Coordinates are normalized to 0-1 range, making them resolution-independent. To convert to pixels, multiply by the page width/height.

Response Structure

The bounding_boxes object in the extraction response contains:
Not all fields will be present in every response. The API only includes arrays for elements that were detected in the document.

Markdown Fields

Use bounding_boxes.markdown_with_ids when you need to correlate text positions with bounding boxes. Use the top-level markdown for clean content display or export.

Example Response

Here’s a real example of the bounding_boxes object from a workbook with an embedded chart, with figure_processing.show_images: true:

Field Descriptions

Text Array

Each text element contains:
  • id: Unique identifier (e.g., txt-1) that links to markdown_with_ids via data-bb-text-id
  • content: The extracted text with prefix (e.g., 0a-NCRI)
  • original_content: The clean extracted text without prefix
  • bounding_box: 8-point coordinate array (may be null for some document types)
  • page_number: Page where the text appears
  • average_word_confidence: OCR confidence score (0-1)
  • selected: Selection state when detect_selections was enabled and the item represents a detected form control or marked-choice region

Title Array

Each title element contains:
  • id: Unique identifier linking to markdown
  • content: The title text with prefix
  • original_content: The clean title text
  • bounding_box: 8-point coordinate array
  • page_number: Page where the title appears
  • average_word_confidence: OCR confidence score (0-1)

Header Array

Each header element contains:
  • id: Unique identifier linking to markdown
  • content: The header text with prefix
  • original_content: The clean header text
  • bounding_box: 8-point coordinate array
  • page_number: Page where the header appears
  • average_word_confidence: OCR confidence score (0-1)
Each footer element contains:
  • id: Unique identifier linking to markdown
  • content: The footer text with prefix
  • original_content: The clean footer text
  • bounding_box: 8-point coordinate array
  • page_number: Page where the footer appears
  • average_word_confidence: OCR confidence score (0-1)

Images Array

Each image element represents a detected chart or embedded image. For PDFs and image inputs, entries are populated when figure detection runs. For spreadsheets, entries are populated for embedded charts and images directly read from the workbook.

Fetching Visual Image Bytes

When you set figure_processing.show_images: true on /extract, every chart/image entry comes back with an image_url pointing at GET /results/{jobId}/images/{filename}. Fetch it with your API key to get the raw PNG/JPEG bytes:
See Get Result Image for the full auth contract — visual image fetches always require same-org x-api-key authentication; there is no anonymous access.

Tables Array

Each table element contains:
  • id: Unique identifier (e.g., tbl-1)
  • bounding_box: 8-point coordinate array
  • page_number: Page where the table appears
  • content: Table content (in HTML format)

Page Number Array

Each page number element contains:
  • id: Unique identifier
  • content: The page number text
  • original_content: The clean page number text
  • bounding_box: 8-point coordinate array
  • page_number: Page where it appears
  • average_word_confidence: OCR confidence score (0-1)
Tables are extracted and returned in HTML format, preserving the structure and making it easy to parse or display.
The id field allows you to link bounding box elements to specific locations in the markdown_with_ids field via data-bb-text-id attributes.

Footnote References

When you enable extensions.footnote_references in your extract request, the response includes an extensions.footnoteReferences array that uses bounding box IDs to link footnote markers to their in-text references. Each entry contains:
  • symbol — the footnote marker (e.g. *, , , 1)
  • footnoteTextId — the id of the footnote explanation, typically found in the Footer array
  • referenceTextIds — an array of id values from the Text, Title, or Header arrays identifying body paragraphs that contain the marker
Use footnoteTextId to look up the footnote’s position and content in bounding_boxes.Footer (or bounding_boxes.Text), and each entry in referenceTextIds to locate the citing paragraphs in bounding_boxes.Text, bounding_boxes.Title, or bounding_boxes.Header. This allows you to spatially highlight both the footnote and every place in the document that references it.
Footnote references are only available for PDF documents. See the Extract endpoint for usage examples.

Converting Coordinates

To convert normalized coordinates to pixel coordinates:

Next Steps

Extract Endpoint

Enable bounding box extraction

Structured Output

Combine with structured data