Feature Snapshot
Summary:
The Verify API Operation is a real‑time TrustedForm API call that checks whether a lead’s certificate meets predefined consent and compliance requirements before the lead is approved for further use.
Key Benefits:
- Confirms every lead meets specific requirements for prior express written consent before contact
- Automates compliance checks to reduce legal risk
- Provides a detailed JSON response with clear outcomes and failure reasons
Typical Use Cases:
- Validating lead consent just before lead purchase or distribution
- Integrating automated verification into CRM systems or lead filter workflows
How the Verify API Operation works
Step‑by‑Step Instructions
-
Obtain the Certificate URL:
Retrieve the unique TrustedForm Certificate URL provided with the lead during the certification process. -
Configure Your API Request:
Prepare an HTTP POST request to the TrustedForm Verify endpoint per the API Documentation. Include mandatory headers such as:
•api-version: 4.0
•Content-Type: application/json
•Accept: application/json
Also, include proper HTTP Basic Authentication credentials using your API key. -
Submit the Verification Request:
Send the POST request with the certificate URL and any optional parameters (for example, lead’s email or phone for fingerprint matching) in the JSON payload. -
Interpret the Response:
The API returns a JSON response with anoutcomefield that indicates “success”, “failure”, or “error”. Additional fields likereasonprovide insight into any issues if the verification fails. -
Act on the Verification Result:
Use the response data to automatically route, approve, or flag leads. If the outcome isfailureorerror, review the reasons and adjust your lead acceptance criteria or request additional vendor data.
Expected Result:
A JSON response displaying an outcome (e.g., "outcome": "success") along with detailed fields such as consent attributes and matching flags.
Validation & Monitoring (optional)
-
Test the Setup: Submit a test lead with a valid TrustedForm Certificate URL and verify that the response returns
"outcome": "success"when all consent criteria are met. - Where to Monitor?: Review results in your API logs for outcome and error details.
Best Practices
- Always include all required headers and correct authentication details in your API requests.
- Test the integration with sample leads before going into production, and build fallback logic to handle
"failure"or"error"outcomes. - Regularly audit your verification criteria and update consent language approvals as regulatory standards or business requirements evolve.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| Consent language not detected in response | Certificate lacks the required consent language | Ensure your lead vendor uses proper consent tagging and confirm certificate configuration. |
| Invalid or missing API credentials | Incorrect API key or missing HTTP Basic Authentication | Verify your API key, username, and header settings match TrustedForm documentation standards. |
| Extended response time or timeouts | Network latency or high server load | Monitor network performance and retry the request; contact support if delays persist. |
| Outcome set to “failure” with detailed reason | One or more verification criteria not met (e.g., font size, opt‑in type) | Review the reason field in the response, adjust verification criteria, and re-test integration. |
Frequently Asked Questions (FAQ)
Q: What exactly does the Verify API Operation do?
A: It examines a TrustedForm certificate to ensure that the lead meets your specified consent and compliance requirements by checking for elements such as approved consent language and proper formatting.
Q: Why is the Verify API Operation important?
A: It automates the critical step of verifying consumer consent, reducing legal and regulatory risks while ensuring that only leads for consumers who have given their consent are contacted.
Q: How do I use the Verify API Operation?
A: By constructing and sending an HTTP POST request to the TrustedForm Verify endpoint with the required headers, certificate URL, and optional lead data. Then, interpret the JSON response to decide if the lead meets your consent criteria.
Q: How fast is the Verify API Operation?
A: It is designed for real‑time processing and typically returns a response in less than 1 second.
Glossary
| Term | Definition |
|---|---|
| Certificate URL | A unique URL provided with every TrustedForm certificate that links to the detailed consent record. |
| Consent Language | The text shown on a lead generation form that informs consumers about the terms under which they are consenting. |
| Outcome | A field in the API response indicating the result of the verification (e.g., success, failure, error). |
| API Operation | A function provided by an API that performs a specific task, such as verifying a certificate in this context. |
Comments
0 comments
Please sign in to leave a comment.