Signatures

Document AI provides two complementary ways to work with signatures:

1. Detected signature regions identify marks and their locations on processed pages.
2. Structured signature results describe the business role and status of expected signatures when the selected extraction configuration includes the signature schema.

Neither capability verifies a signer's identity or determines the legal validity of a signature.

Detected signature regions

Completed documents can expose detected signatures through the investigation endpoints. Each item identifies its page, result, and normalized location.

curl \
  "https://sandbox-api.shipwell.com/document-store/documents/<document-id>/signatures" \
  -H "Authorization: Token <user-token>"

import requests

response = requests.get(
    "https://sandbox-api.shipwell.com/document-store/documents/<document-id>/signatures",
    headers={"Authorization": "Token <user-token>"},
    timeout=30,
)
response.raise_for_status()
signatures = response.json()

Each item includes a page_number, result_id, and normalized geometry.

Use optional run_id or result_id query parameters to inspect one processing attempt or split result.

Structured signature results

All platform-managed configurations include a signature extraction schema. It can return one entry for each expected execution role.

A structured signature value can include:

• role — such as shipper, carrier driver, consignee receiver, customer, vendor, or authorized representative
• status — present , absent , or unclear
• signer_name and signer_title , when readable
• organization
• Printed signing date or time
• method — handwritten, electronic, stamp, initials, or unknown

The selected configuration defines which document context is considered. For example, Shipment Operations emphasizes transportation execution roles, while Carrier Compliance covers agreements and compliance forms.

Which signature surface should I use?

Use detected regions when you need to:

• Draw every detected signature mark in a document viewer
• Count possible signatures by page
• Review spatial evidence without applying a business role

Use structured results when you need to:

• Determine whether an expected role appears signed
• Distinguish shipper, carrier, receiver, taxpayer, or representative roles
• Integrate signature status into a review workflow
• Read signer details when the source supports them

For high-impact workflows, show the structured result together with its source region.

Proof-of-delivery workflow

1. Process a proof of delivery with Shipment Operations or Universal Logistics.
2. Wait for the run to reach completed .
3. Find signature entries in the result's schemas .
4. Retrieve /signatures or the relevant page to display the evidence.
5. Route absent or unclear expected signatures for human review.

Important limitations

• A detected mark is not proof of signer identity.
• An empty signature list does not prove that a document is unsigned.
• Printed text near an empty signature line should not be treated as a signature.
• Low-quality scans can produce an unclear result.
• Always retain human review for legal, compliance, payment, or claims decisions.