A successful API response confirms what VIF supplied. It does not, by itself, confirm that Nexgen received, stored, interpreted, or displayed the information correctly.
Validate the VIF response
Use Postman to send the same type of authorized API request expected from Nexgen, following your established integration procedure. Inspect the raw JSON and confirm:
The request reaches VIF successfully.
The correct account is located.
Expected profile, contact, address, and individual information is returned.
Expected conditions, accommodations, and responder-access indicators are present.
Missing optional information is represented consistently as null or an empty value.
Script-derived values match the organization's approved API mapping.
Validate the Nexgen side
Review Nexgen application/integration logs and user-interface field mappings to establish whether Nexgen received, interpreted, and displayed the returned information correctly.
The supplied guide does not provide Nexgen menu paths or configuration instructions. Do not infer that a successful Postman test completes end-to-end validation.
Avoid copied-response formatting problems
Inspect and validate the raw response in Postman. The source notes that copying JSON through email or a rich-text editor can introduce formatting changes.
Common questions
Postman returned the right information. Is the integration fully validated? No. Nexgen receipt, interpretation, and display still need to be checked.
Does an empty optional field mean the API failed? Not automatically. It can indicate unavailable or unsupplied information.
Should every organization return the same script-derived answers? No. Organizations can have different approved mappings.
Still need help?
Contact us