Resubmission Workflow

Resubmission is optional. Most customers send one evaluate and never use this page.

Question	Answer
What is it?	A second (or later) `POST /evaluate` with corrected mapped JSON — `record.record_json` + `submission_type: "resubmit"`. You omit XML. The response shape matches the first call.
Why care?	Candidate identity or charge data was wrong or incomplete on the first run, and you want a new decision after fixing the mapped payload — without replaying vendor XML.
Don’t care?	Skip this guide. Integrate XML or JSON once (Quickstart / How It Works) and process the decision.

When you do use it: send record.record_json only (no record.xml). Provide exactly one of xml or record_json on every /evaluate call.

When to Use Resubmission

Scenario	Path
First evaluation from vendor XML	Initial submission (`record.xml`)
First evaluation from mapped JSON	Initial / JSON-native (`record.record_json` + `submission_type: "resubmit"`)
Re-evaluation after correcting mapped criminal data	Resubmission (`record.record_json`) — no XML
Re-evaluation after updating candidate identity	Resubmission (`record.record_json`) — no XML

How Resubmission Differs from Initial Submission

Field	Initial (XML)	Resubmission (JSON)
`record.xml`	Required	Omit (not used; sending both `xml` and `record_json` fails validation)
`record.record_json`	Omit	Required
`record.submission_type`	Omit	`"resubmit"` (required with `record_json`)
`record.candidate_info`	Recommended	Required
`record.search_id`	Required	Required
`record.search_date`	Required	Required
`record.order_id`	Required	Required
`record.order_number`	Required	Required

The response shape is identical for both paths.

Step-by-Step

1. Prepare the Corrected Record JSON

The record_json object must include a top-level criminal_search_results key with the corrected criminal data. Important placement rules:

candidate_info, submission_type, order_id, and order_number must be sibling fields on record — not nested inside record_json
record_json must not contain candidate_info, submission_type, order_id, or order_number

2. Build the Request

{
  "record": {
    "search_id": "76190bc0-e58c-494f-92c5-0c9a47389528",
    "search_date": "2025-04-30",
    "order_id": "41115779",
    "order_number": "41115779.1",
    "submission_type": "resubmit",
    "record_json": {
      "criminal_search_results": {
        "courts": [
          {
            "cases": [
              {
                "case_number": "MJ-05003-TR-0006023-2020",
                "jurisdiction_state": "PA",
                "offenses": [
                  {
                    "charge": "DRIVING WHILE OPERATOR PRIVILEGES SUSPENDED",
                    "disposition": "GUILTY",
                    "offense_date": "2020-03-10",
                    "type_class": "SUMMARY"
                  }
                ]
              }
            ]
          }
        ]
      }
    },
    "candidate_info": {
      "first_name": "John",
      "last_name": "Doe",
      "date_of_birth": "1990-05-15",
      "ssn": "123-45-6789"
    },
    "applicant_state": "CA"
  }
}

3. Submit the Request

curl -X POST "$PR_API_BASE/evaluate" \
  -H "Authorization: Bearer $PR_TOKEN" \
  -H "Content-Type: application/json" \
  --data @resubmit.json

import requests, os

base = os.environ["PR_API_BASE"]
token = os.environ["PR_TOKEN"]

resp = requests.post(
    f"{base}/evaluate",
    headers={
        "Authorization": f"Bearer {token}",
        "Content-Type": "application/json"
    },
    json=payload
)
result = resp.json()

4. Interpret the Response

The response uses the same structure as an initial submission. See Evaluate endpoint for the full response reference and Quickstart — Step 5 for field explanations.

Common Mistakes

Mistake	Result
Nesting `candidate_info` inside `record_json`	Validation error
Nesting `order_id` or `order_number` inside `record_json`	Validation error
Omitting `submission_type: "resubmit"` when using `record_json`	Validation error
Sending both `xml` and `record_json`	Validation error
Putting `submission_type` inside `record_json.search`	Validation error

Evaluate endpoint — Full request/response reference for both paths
Quickstart — Initial submission walkthrough
Troubleshooting — Common issues and resolution steps

Core Concepts

Guides

Examples

Support

Resubmission Workflow

When to Use Resubmission

How Resubmission Differs from Initial Submission

Step-by-Step

1. Prepare the Corrected Record JSON

2. Build the Request

3. Submit the Request

4. Interpret the Response

Common Mistakes

​When to Use Resubmission

​How Resubmission Differs from Initial Submission

​Step-by-Step

​1. Prepare the Corrected Record JSON

​2. Build the Request

​3. Submit the Request

​4. Interpret the Response

​Common Mistakes

​Related

When to Use Resubmission

How Resubmission Differs from Initial Submission

Step-by-Step

1. Prepare the Corrected Record JSON

2. Build the Request

3. Submit the Request

4. Interpret the Response

Common Mistakes

Related