Skip to main content

​
Which API do I use?

Ping.Extraction is a standalone product that performs automated processing and structuring of insurance documents. Ping.Data is another standalone product that collects data, handles geocoding, and manages AI interaction for small or large batch requests. Ping.Vision manages submission workflows, part of which is invoking Ping.Extraction when appropriate. Ping.Vision requires customization to meet your organizational workflow needs and then manages the use of Ping.Extraction and Ping.Data. All of these products are available for direct use. However, most use cases will interface with only one of them directly, as that product will handle any required integrations.

​
How do I authenticate?

Authentication tokens for Ping.Vision and Ping.Extraction can be generated here: https://auth.pingintel.com/account/api_keys/. The same token works in both production and staging environments. Other APIs currently use different tokens. Please contact support to request authentication tokens for those APIs.

​
Common workflows

Each workflow page walks through a full API call sequence with runnable code. New to SOV processing? Start with How Ping Processes SOVs for the behavior behind these calls, and Concepts & Identifiers for the terms they use.

​
Ping.Extraction

  • Process an SOV — parse a new workbook for the first time and download the generated outputs.
  • Get or Create an SOV Output — request an additional format, or regenerate an output, from an already-parsed SOV.
  • Update an SOV — apply corrected building attributes to a parsed SOV, or trigger a SCRUB reoutput.
  • Monitor SOV Activity — track every SOV and SUD processed across your account with a single cursor-paginated poll.
  • Build an SOV Pipeline — submit jobs, apply updates, and download outputs from one long-running polling loop.

​
Ping.Data

​
Ping.Vision