SmartAdvocate

Retry Smartadvocate Intake Draft Steps

Changed on

Re-run promote steps against an already-created case.

For a promoted draft whose case exists but where an enrichment step failed (a rejected id, a transient SA error). Contact and case creation are never re-run — the promoter sees the ids already on the draft and reports them as already created. Steps not re-run keep their previous outcome.

post/smartadvocate/intake-draft/{smartadvocate_intake_draft_id}/retry-steps

Request

  • Base URL: https://api.openintake.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.openintake.ai/smartadvocate/intake-draft/{smartadvocate_intake_draft_id}/retry-steps
  • Auth: none declared

Path parameters

smartadvocate_intake_draft_idstring uuid required

Request body

step_keysstring[] nullable

Steps to re-run; omit to re-run every step that failed on the last attempt

enrichmentobject nullable

Corrected enrichment to use for the retry; omit to reuse the draft's stored enrichment

Response

Successful Response

smartadvocate_intake_draft_idstring uuid required
call_idstring uuid required
first_namestring nullable
last_namestring nullable
emailstring nullable
phone_numberstring nullable
date_of_birthstring date nullable
genderstring nullable
address_line1string nullable
citystring nullable
statestring nullable
zip_codestring nullable
case_summarystring nullable
incident_datestring date nullable
incident_statestring nullable
case_type_hintstring nullable
matched_sa_contact_idinteger nullable

Existing SA contact matched by the caller's phone number; promotion attaches the case to it instead of creating a new contact

matched_sa_contact_namestring nullable
ambiguous_contact_matchboolean

Multiple person contacts share the caller's phone number; the match shown is a best guess and needs manual review

duplicate_case_numbersstring[]

Existing case numbers on the matched contact with the same incident date (likely repeat caller about the same accident)

existing_case_candidatesobject[]

Cases staff opened recently for a caller like this one, found live in SA at promote time [{sa_case_id, case_number, case_name, created_date, phone_matched, name_score, plaintiff_names}]

existing_case_decisionstring nullable

How the merge target was chosen: phone_and_name | llm | none | manual | error (error = held for a human, nothing written)

existing_case_reasonstring nullable
merged_into_existingboolean

The intake was merged into an existing case (sa_case_id) instead of creating one

statusstring
sa_contact_idinteger nullable
sa_case_idinteger nullable
sa_case_numberstring nullable
was_dry_runboolean nullable
auto_promotedboolean
enrichmentobject nullable

Rich extraction: plaintiff role, injuries, treatment, medical providers, insurance, vehicle, referral source and tags (see DraftSmartAdvocateEnrichment)

promote_stepsobject[] nullable

Per-step promote outcomes [{key, label, status: ok|skipped|failed, detail, sa_id}]; failed steps can be re-run via the retry-steps endpoint

created_atstring date-time required
updated_atstring date-time nullable

Changes

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      endpoint added