Please refer the following document for the detailed prefill API specification
On performing the below launch request in browser, Partner will be redirected to the Next Connect funnel.
Please refer to the signature generation section for further information about generating the signature parameter.
|NEXT funnel will be launched as an HTML page|
Partner will have an POST API that accepts the status updates from NEXT. Following will be the payload that NEXT will send to PARTNER for status updates on the policy.
“partnerRequestId”: <unique partnerRequestId used in pre fill app generation>,
|Response code of 200 should be returned for Success|
For failure, please follow standard the HTTP status codes
Following are the values that statuses can assume
data-pft=“#pft token received from prefill api response#” – this is optional
data-pfr=“#pre_fill_request received from prefill api response#” – this is optional
data-partner-request-id=“#LegalZoom’s customer id which gets sent in prefill request#”>
Next will provide api keys specific to each environment that can be used for signature generation. Signature is passed in the api headers. Please follow the instructions in this doc to generate the signature.
We will review and follow Partner’s security implementation for status updates