OPopenintake
SmartAdvocate

Preview Smartadvocate Intake Draft

Changed on

Plan a promote without writing anything to SmartAdvocate.

Resolves every picklist value, builds every request body and returns the step plan plus the configured defaults BY NAME. Writes nothing, so unlike promote it is open to non-developers and needs no intake push mode. It does read SA live for cases staff opened recently for this caller, and may ask an LLM which one is theirs: merge_target is the case a promote would merge into. merge_into_case_id / force_new_case preview the dialog's choice instead of the automatic one.

get/smartadvocate/intake-draft/{smartadvocate_intake_draft_id}/preview

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}/preview
  • Auth
    none declared

Path parameters

smartadvocate_intake_draft_idstring uuid required

Query parameters

case_group_idinteger nullable
case_type_idinteger nullable
merge_into_case_idinteger nullable
force_new_caseboolean

Response

Successful Response

plan_onlyboolean
payloadsobject

The raw SmartAdvocate request bodies that would be sent (developer view)

defendant_contact_namestring nullable
matched_sa_contact_idinteger nullable

Existing contact the case would attach to instead of creating a new one

duplicate_case_numbersstring[]
intake_datestring nullable

Intake date the case would carry, in the firm's local calendar

blocked_reasonstring nullable

Why a promote would be refused right now (duplicate case, missing case group/type)

merge_targetobject nullable

The recently opened case this promote would merge into {sa_case_id, case_number, case_name, created_date}; null = a new case is created

existing_case_candidatesobject[]

Every recently opened case that could be this caller's, for the dialog's merge choice

existing_case_decisionstring nullable
existing_case_reasonstring nullable
identity_review_reasonstring nullable

Why staff must confirm who the plaintiff is (ambiguous or conflicting contact match); promote with confirm_identity

Changes