Developer guide
Your integration supplies the application activity that VeriProof evaluates and records. As a Developer, you connect that integration, check its evidence, and investigate reporting errors. Authorized owners remain responsible for governance and business decisions.
Prepare the application
Confirm the VeriProof application, environment, owner, endpoint, and approved SDK package. Store the issued application key in a secret manager.
Use separate VeriProof applications when environments need independent access or evidence records.
Capture representative work
Start with the core SDK and add adapters for the frameworks your application uses. The approved use case determines which session, decision, risk, oversight, outcome, and correlation fields you need to record.
Do not add fields only to improve a score. Each value should reflect application behavior and have a clear source.
Verify reporting
- Send a non-production session through the intended application path.
- Confirm it appears under the correct application.
- Review the captured steps and field provenance.
- Check SDK health, errors, and expected signal coverage.
- Test failure and retry behavior before broader use.
Protect sensitive data
Check what the integration may send, including prompts, responses, metadata, attachments, and error details. Remove sensitive data that is not needed before it leaves the application.
Test supported redaction with representative non-production records. Pattern-based protection does not identify every sensitive value.