Skip to main content
POST
/
api
/
v1
/
submission
/
{id}
/
sovfixer-parse
Parse Documents via Ping.Extraction
curl --request POST \
  --url https://vision.pingintel.com/api/v1/submission/{id}/sovfixer-parse \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "filenames": [
    "<string>"
  ],
  "sovfixer_request_type": "WORKING_SOV",
  "sovfixer_request_type_notes": "<string>"
}
'
{
  "message": "<string>",
  "sovid": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.pingintel.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Supports Token-prefixed API keys and Bearer-prefixed JWT-based authentication.

Path Parameters

​
id
string
required

The pingid of the submission.

Body

​
filenames
string[]
required

List of filenames to parse. Filenames are references to documents that are already attached to the submission.

​
sovfixer_request_type
enum<string> | null

Optional selection for the type of SOV to request.

  • WORKING_SOV - Working SOV: Simplified or preprocessed copy of the original submission doc, with the intent of allowing Extraction to work more smoothly.
  • UPDATED_SOV - Updated SOV: Revised submission with updated data, such as a quarterly schedule update or with completed exposure data.
  • OTHER - Other: Please provide details in the sovfixer_request_type_notes field.
Available options:
WORKING_SOV,
UPDATED_SOV,
OTHER,
null
​
sovfixer_request_type_notes
string | null

Free-form notes when request type is 'OTHER'

Response

​
message
string
required

Message indicating the status of the request.

​
sovid
string
required

SOVID identifier returned by Ping.Extraction to track the fixing job.