Feature Snapshot
Summary:
The Retain API Operation is a TrustedForm feature that securely stores a certificate in your account, providing verifiable, long‑term evidence of how a lead was generated.
Key Benefits:
- Offers reliable evidence to help evaluate compliance with telemarketing and advertising regulations
- Supports compliance audits by retaining detailed records of lead events
- Enables real‑time integrations with external system to automate record keeping processes
Typical Use Cases:
- Retaining certificates for legal defense and audit documentation
- Automating certificate storage during lead generation flows
- Rejecting leads when a TrustedForm certificate can not be retained
How the Retain API Operation works
When a TrustedForm certificate is generated during a consumer’s session, the Retain API Operation stores that certificate in your account for future retrieval after receiving a request in accordance with the API Documentation. The operation returns a JSON response that confirms whether the certificate was successfully retained for compliance and audit purposes.
Step‑by‑Step Instructions
-
Configure your API Request:
• Add the headerapi-version: 4.0to signal the use of the latest API schema.
• Use HTTP Basic Authentication with “API” as the username and your API key as the password.
• Confirm that your TrustedForm account is enabled for certificate retention. -
Prepare the JSON Payload:
• Include an object named"retain"(even if empty) to initiate storage of the certificate.
• Also include the"match_lead"object with an"email"and/or"phone"operation, which will perform lead matching against the certificate. -
Send the HTTP POST Request:
• Post your request to the TrustedForm Certificate URL (formatted ashttps://cert.trustedform.com/<cert_token>).
• Ensure the request includesContent-Type: application/jsonandAccept: application/jsonheaders. -
Process the Response:
• On success, the API returns an HTTP 200 status code with a JSON object containing certificate details and an “outcome” field set to “success”.
• If errors occur, review the JSON error details to troubleshoot the issue.
Expected Result:
The certificate is successfully retained in your TrustedForm account. The API response includes all pertinent certificate details, an outcome field indicating “success”, and any matching data if lead matching is enabled.
Validation & Monitoring (optional)
-
Test the Setup:
Make a sample API call using a valid TrustedForm certificate URL and verify that you receive an HTTP 200 response with the expected JSON payload containing certificate details. -
Where to Monitor?:
Monitor your TrustedForm Retained Certificates and check API logs to track the outcome and review any error codes for further troubleshooting.
Best Practices
- Always verify the certificate URL begins with
https://cert.trustedform.com/to maintain secure communications. - Include both the
"retain"and"match_lead"objects when you want to automatically verify lead data. - Store the complete certificate URL with your lead data in your CRM for future audit reference.
- Log every API response (successes and errors) to identify and resolve integration issues promptly.
- Regularly review the TrustedForm API Documentation to ensure your integration adheres to current API specifications and error code updates.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| HTTP 0 or request timeout | Network connectivity issues or client-side timeout settings | Verify network stability and adjust timeout settings; retry the request |
| HTTP 400 or 406 (bad request) | Incorrect certificate URL formatting or missing required parameters | Verify the certificate URL format and ensure the JSON payload meets API specifications |
| HTTP 402 (Payment Required) | Account billing or subscription restrictions | Check your account’s billing status and resolve any payment issues |
| HTTP 403 (Forbidden) | Incorrect API key or authentication failure | Confirm that you are using the correct API key and proper HTTP Basic Authentication |
| HTTP 404 (Not Found) | Certificate expired or invalid URL | Ensure the certificate is current and the URL is correct; do not retry expired certificates |
| HTTP 405 (Method Not Allowed) | Certificate generated in Sandbox mode | Use a production certificate instead of a sandbox certificate |
| HTTP 410 (Gone) | Certificate retention window has expired | Do not retry; the certificate is no longer eligible for retention |
| HTTP 500, 502, or 503 (Server Errors) | Temporary server issues or internal errors | Retry the request; if the problem persists, contact TrustedForm support |
Frequently Asked Questions (FAQ)
Q: What is the Retain API Operation?
A: It is the TrustedForm Certificate API operation used to store a TrustedForm certificate in your account, providing independent record of lead generation for compliance and audit purposes.
Q: Why is the Retain API Operation important?
A: Retaining certificates enables you to securely document how and lead was generated and if consent was given to support regulatory compliance with legal standards like the TCPA.
Q: How do I use the Retain API Operation?
A: To use it, include the api-version: 4.0 header in your HTTP request, authenticate using your API key, and send a JSON payload with the "retain" and "match_lead" objects to a TrustedForm Certificate URL via an HTTP POST request.
Q: How fast is the Retain API Operation?
A: Under normal conditions, the API typically responds within 1 to 2 seconds, providing near real‑time feedback on the retention process.
Glossary
| Term | Definition |
|---|---|
| Retain | The operation of storing (or claiming) a TrustedForm certificate in your account, serving as verifiable proof of consumer consent. |
| TrustedForm | A service that captures and stores documentation of user interactions and consent during lead generation, resulting in a certificate. |
| Certificate URL | The unique URL provided with each TrustedForm certificate, typically formatted as https://cert.trustedform.com/<cert_token>. |
| Match Lead | An optional operation that compares the lead’s provided contact details (email, phone) with data captured in the certificate to ensure consistency. |
| HTTP POST | The method used to submit data (such as a certificate retention request) to the TrustedForm API. |
| API Version | The version of the TrustedForm API in use, specified via the api-version header (e.g., 4.0) to enable current features. |
Comments
0 comments
Please sign in to leave a comment.