iClaim Record API Overview

The iClaim Record API allows developers to programmatically access and manage iClaim platform features. From claiming and storing records to verifying contact details, this API provides secure, scalable endpoints for seamless integration with external systems, enabling efficient workflows and real-time data interaction.

Designed to support both technical implementation and strategic business goals, this API provides a powerful foundation for data ownership, compliance, and campaign optimization.

The iClaim Record API is built with practical integration and scalability in mind, giving customers the tools to automate processes, enhance targeting, and meet evolving regulatory standards. 

Its modular structure allows each operation—Claim, Confirm, Lead Snapshot, Lead Contact Check, and Batch Request—to be used independently or in combination, offering flexibility across workflows and environments. Whether you are focused on compliance, performance, or data enrichment and quality, iClaim helps you build smarter lead pipelines.

 

Claim Operation

The Claim Operation is a core feature of ValidRecord’s iClaim component, designed to help clients securely claim, store, and access lead data over time. This is particularly important for maintaining compliance with data retention policies, as claimed records are securely stored for up to 5 years. 

The API request requires specific parameters, including your ValidRecord account ID, API token, and Record ID. 

You can view the API Documentation for the Claim operation along with all the possible request and response examples via the API Documentation > Record API > Claim section. 

Read more about the iClaim Claim API section in the following article. 

 

To improve record classification and attribution, the iClaim Claim API allows you to include extra fields:

  • Reference: A free-text field for storing identifying details, such as a unique user ID, session token, or the referring URL.
  • Vendor: Used to specify the name of the company or partner that delivered the lead associated with the recording.

After a successful claim request, the API response provides the following details:

  • The vendor and reference values submitted
  • The Record URL for future access
  • The claim result status
  • Whether the claim is unique (i.e., the first claim for this Record ID)
  • The expiration timestamp for record access

Benefits of using the Claim API: 

  • Data Retention & Compliance: Securely store lead data for up to 5 years, while fulfilling regulatory requirements and maintaining an auditable and verifiable record trail.
  • Custom Integration Flexibility: Perfect for integrating with internal systems, especially when off-the-shelf solutions like automatic claiming don’t align with your workflows.
  • Improved Tracking & Attribution: Optional parameters (reference and vendor) allow clients to tag, filter, and analyze data more effectively, leading to better decision-making and reporting.
  • Access Control & Security: API token authentication ensures only authorized systems or users can make claim requests.
  • Clarity & Accountability: Every claim response includes detailed metadata to confirm claim status, uniqueness, and expiration, helping maintain visibility into your process. The response provides clear indicators on the success and uniqueness of each claim, helping diagnose integration issues or detect duplicate claims.

 

Confirm Operation

The Confirm Operation helps you ensure your leads are fully compliant with consent requirements such as the TCPA (Telephone Consumer Protection Act) and other regulatory standards. By securely verifying your leads, you can confidently meet legal requirements and reduce the risk of non-compliance.

This operation allows you to verify that a lead includes the appropriate consent language before further processing or distribution. It can also confirm whether or not the lead consented to be contacted by a specific advertiser. Lead verification through the Confirm API is essential for businesses focused on regulatory compliance and risk mitigation. It’s especially useful for lead buyers and sellers who must demonstrate proof of consent in environments where TCPA guidelines are enforced.

The API request requires specific parameters, including your ValidRecord account ID, API token, and record ID. 

You can view the API Documentation for the iClaim Confirm Operation along with all the possible request and response examples via the API Documentation > Record API > Confirm section. 

Read more about the iClaim Confirm API in this article. 

To improve record classification and attribution, the iClaim Confirm API allows you to include the information about the advertiser (the Advertiser Operation, which allows you to send the name of the advertiser along with the request. This field is used to perform a one-to-one consent language check.

After a successful confirm request, the API response provides the following details:

  • The status of the request
  • The advertiser’s name listed in the request. 
  • The list of detected consent languages
  • The operation status of the Confirm request
  • The consent approval status, if any of the detected languages meet compliance requirements
  • The one-to-one field that returns a null value when the Advertiser parameter is missing or no consent language is found. 

Benefits of using the Confirm API: 

  • Regulatory Compliance: Helps you meet one-to-one consent standards and TCPA requirements by verifying consent language in lead data.
  • Advertiser-Level Validation: Adds context to lead verification by associating consent checks with specific advertisers.
  • Risk Reduction: Minimizes the chances of non-compliant data being processed or sold.
  • Clear Response Feedback: Provides detailed output on consent detection, approval status, and operation results for greater transparency.
  • Flexible Integration: Designed for well-aligned use within existing systems or workflows that require consent verification.

 

Lead Snapshot Operation

The iClaim Lead Snapshot operation allows you to obtain additional lead data on every purchased lead, including insights such as lead origin, domain, browser, device type, input methods, and more—supporting lead optimization and strategic decision-making from the available Record. 

The Lead Snapshot API is designed to enhance lead intelligence by delivering context that helps verify, qualify, and prioritize leads. This service is ideal for lead buyers who want to maximize the value of each lead by understanding who the lead is, how they behaved, and where they came from.

As soon as the user purchases the record and becomes the paid client, the Lead Snapshot data, such as the last lead activity age, lead origin, geolocation based on the lead IP address, the names, and versions of the used operating systems and browsers, data that the user inputs, and more become available for this client.  

The API request requires specific parameters, including your ValidRecord account ID, API token, and Record ID. 

You can view the API Documentation for the iClaim Confirm operation along with all the possible request and response examples via the API Documentation > Record API > Lead Snapshot section. 

Read more about the Lead Spanshot API in this article. 

The Lead Snapshot API also supports advanced content analysis operations to help further validate or filter records based on the content of the lead page:

  • Scans: Performs a flexible search for specific words or phrases within the record’s page content. Useful for keyword detection or flagging custom criteria.
  • Required: Searches for specific required text within the page content. The search is case- and whitespace-insensitive and supports wildcards using {{*}}.
  • Forbidden: Identifies any forbidden text present on the page. Like Required, this search is case- and whitespace-insensitive and supports wildcard matching.

After obtaining a successful Lead Snapshot request, the API response provides the following response details:

  • Global Response Fields
  • Record Identification & Timing
  • Activity & Duration
  • Domain & Vendor Info
  • IP & Geolocation
  • Browser & OS Info
  • User Behavior Records and Data
  • Framing & URLs
  • Text Scanning Results

Benefits of using the Lead Snapshot API:

  • Improved Lead Scoring & Qualification: Access detailed behavioral and technical metadata, including last age, browser, origin, OS, and geolocation, to prioritize leads more effectively.
  • Implemented Quality Assurance Through Content Scanning: Scan the lead page for specific keywords, mandatory terms, or forbidden content to align with your quality standards or compliance checks.
  • Enhanced Operational Efficiency: Integrate rich lead data directly into your systems to streamline processing, boost automation, and reduce manual qualification steps.
  • Increased Lead Confidence: Get a full breakdown of user behavior and environment, adding trust and traceability to every lead purchase.

 

Lead Contact Check Operation

The Lead Contact Check Operation allows you to cross-reference a lead’s contact data – specifically their email and/or phone number— against the values captured during the lead’s recorded interaction. This ensures that the lead data you’re working with is accurate and matches the information collected during the initial interaction, helping protect you from lead fraud and reducing the risk of potential legal action. 

Additionally, integrating Lead Contact Check into your lead processing flow enhances data integrity and operational efficiency. It enables the automated filtering of incomplete or incorrect submissions, improves downstream analytics, and supports more effective targeting in marketing and sales pipelines.

This check is executed via a dedicated API endpoint, providing reliable verification within automated workflows. 

You can view the API Documentation for the iClaim Lead Contact Check operation along with all the possible request and response examples via the iClaim > API Documentation > Record API > Lead Contact Check section. 

Read more about the Lead Spanshot API in this article. 

The Lead Contact Check API also supports the email and/or phone check operations (optionally):

  • Email: Customer’s email or SHA1-hash (please downcase email before hashing)
  • Phone: Customer’s phone or SHA1-hash (please remove all non-digit characters before hashing)

After obtaining a successful Lead Contact Check request, the API response provides the following response details:

  • The email address or phone number (or its hashed value) provided in the request.
  • The result details of the operation indicate whether the submitted email or phone number was found in the form data.

Benefits of using the Lead Contact Check API:

  • Fraud Prevention: Ensures that lead data is accurate and verifiable, reducing the risk of lead fraud and helping protect your organization from potential legal action.
  • Accurate Contact Matching: Confirms whether the phone or email matches what was actually typed into the lead form, helping you avoid follow-ups with invalid or misattributed data.
  • Automated Lead Validation: Automates the verification step, allowing your system to instantly flag or reject mismatched leads without manual oversight.
  • Support for Secure Workflows: Use hashed values for email or phone to maintain data security while still validating submissions.
  • Actionable Insights in Real-Time: The API delivers instant, clear feedback on whether a contact detail was found, keeping your lead pipeline efficient and trustworthy.

 

Batch Request Operation

The Batch Request Operation allows you to combine a couple of operations, such as claim, confirm, lead contact check, and lead snapshot, into one API request. 

Integrating all available operations that are available via API simplifies the process of obtaining necessary lead data and allows users to create one API request that includes all parameters and multiple operations required. 

You can view the API Documentation for the Lead Batch Request API operation along with all the possible request and response examples via the iClaim > API Documentation > Record API > Batch Request section. 

The Lead Batch Request API supports all operations that are described in the sections above, such as claim, confirm, lead snapshot, and lead contact check. 

Benefits of using the Lead Batch Request API:

  • Streamlined API Workflow: Combine multiple operations, such as claim, confirm, contact check, and lead snapshot, into a single request to reduce overhead and simplify development.
  • Efficiency & Performance: Reduce the number of API calls, minimize latency, and optimize system performance for high-volume lead flows.
  • Improved System Efficiency: Minimize the number of API calls needed, reducing network load, request limits, and integration complexity.
  • Cleaner Integration Architecture: Simplifies backend logic by bundling required steps into one centralized operation, reducing code complexity.
  • Consistent & Synchronized Data: Ensure all operations are performed on the same lead data simultaneously, improving consistency and reducing the risk of data mismatch.
  • Reliable & Scalable: Ideal for teams looking to scale lead handling operations while maintaining accuracy, speed, and control.
Categories: iClaim