Lead generators and lead buyers
For those who need TCPA evidence to travel with the leads they sell or buy.
The two roles
Lead generator. Runs the website with the consent form. Installs the SDK, captures the CDR when a consumer submits, and hands the evidence to whoever buys the lead.
Lead buyer. Receives a lead and a share URL. Never touches the SDK. Makes one API request to pull the evidence into their own account, optionally refusing it if it does not meet their requirements.
These are roles, not account types. One organization commonly does both, so there is one set of docs and you use the parts you need.
Who pays, and who can download
A CDR is billed to each organization that collects it, and collecting is what grants download access. So billing and access are the same question.
- You capture it. With auto-collect on, which is the default once billing is set up, you are the payer for records captured on your own sites. Without auto-collect, you are not billed for CDRs, and you cannot download them- you can only share them.
- A buyer opens a share URL you created after you paid. They get access free. You can hand the same record to as many direct partners as you like at no extra cost.
- A buyer opens a share URL from an organization that never paid. They collect the record themselves and are charged for it.
Access is tracked per organization, so the API answers whether your organization can download a record rather than whether the record is downloadable. Access and collection covers the rest.
What each role does next
If you are capturing evidence, start with the quickstart. If someone sent you a share URL and a lead, you need an API key and a single POST, and none of the SDK pages apply.