This page is for intakeIntakeThe process a law firm or its intake team uses to screen a potential client, collect the facts of the accident and injury, and decide whether to take the case. Glossary managers, developers and buying desks that want to see a car accident lead before the first call. The fields below are the ones on Summit’s car accident leads. The exact field specification (field names, formats, required and optional fields) is shared during onboarding, so treat this page as a preview, not the specification itself.
Car accident lead fields
The fields are grouped by what a buyer uses them for. In the "Example" column, accident and injury questions show where the claimant’s answer goes rather than a value: the answer formats are set in the field specification.
Contact fields
| Field | What it is | Example |
|---|---|---|
first_name | The consumer’s first name, as entered on the form. | Jordan |
last_name | The consumer’s last name. | Example |
email | The consumer’s email address. | jordan.example@example.com |
phone | The consumer’s phone number. | 555-0142 |
Location fields
Car accident leads carry the state, ZIP code, city and county, not a street address.
| Field | What it is | Example |
|---|---|---|
state | Two-letter state code. Buyers filter on it. | NV |
zip_code | Five-digit ZIP code. Buyers set coverage down to the ZIP code. | 89101 |
city | City where the consumer is located. | Las Vegas |
county | County where the consumer is located. | Clark |
Accident and injury fields
These eight fields are the qualifier fields for the verticalVerticalThe industry or product category a lead belongs to, such as roofing or car accident. Glossary. Together they tell a buyer when the accident happened, what kind it was, whether the claimant was hurt and treated, who the claimant says was at fault, and whether a lawyer is already involved.
| Field | What it is | Example |
|---|---|---|
injury | Whether the consumer reports an injury from the accident. | The consumer’s answer on the form |
at_fault | Whether the consumer says they were at fault. | The consumer’s answer on the form |
accident_type | The kind of accident the consumer reports. | The consumer’s answer on the form |
accident_date | The date of the accident. Buyers use it to see how recent the accident is. | 2026-09-28 |
doctor_treated | Whether a doctor has treated the consumer for the injury. | The consumer’s answer on the form |
serious_injury | Whether the consumer describes the injury as serious. | The consumer’s answer on the form |
represented | Whether the consumer already has a lawyer for this accident. | The consumer’s answer on the form |
case_description | What happened, in the consumer’s own words. | TEXT_ENTERED_BY_CONSUMER |
Consent record fields
| Field | What it is | Example |
|---|---|---|
landing_page_url | Address of the page where the form was submitted. Part of the consent record. | https://www.example.com/request |
xxTrustedFormCertUrl | Link to the TrustedForm certificate for the form session, a third-party record of the submission that a buyer can open and keep. | https://cert.trustedform.com/EXAMPLE |
xxTrustedFormPingUrl | A second TrustedForm link, used to check that the certificate exists before it is kept. | https://ping.trustedform.com/EXAMPLE |
tcpa_text | The opt-in language the consumer saw next to the submit button. Part of the consent record. | OPT_IN_TEXT_SHOWN_TO_CONSUMER |
user_agent | The browser and device description sent by the device that submitted the form. | Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) |
submission_time | Date and time the consumer submitted the form. Part of the consent record, and the way a buyer sees how old a lead is. | 2026-10-01T14:32:10Z |
ip_address | IP address of the device that submitted the form. Part of the consent record. | 192.0.2.44 |
xxTrustedFormToken | The TrustedForm certificate ID, the last part of the certificate link. | EXAMPLE |
Sample car accident lead, filled in
The same fields, filled in for one invented claimant. Accident and injury answers are shown as FORM_ANSWER, the opt-in languageOpt-in languageThe consent disclosure shown next to the submit button on a lead form. Glossary as a placeholder, and the TrustedForm links point to an EXAMPLE certificate that does not exist.
Example values. Not a real consumer.
| Field | Example value |
|---|---|
first_name | Jordan |
last_name | Example |
email | jordan.example@example.com |
phone | 555-0142 |
state | NV |
zip_code | 89101 |
city | Las Vegas |
county | Clark |
injury | FORM_ANSWER |
at_fault | FORM_ANSWER |
accident_type | FORM_ANSWER |
accident_date | 2026-09-28 |
doctor_treated | FORM_ANSWER |
serious_injury | FORM_ANSWER |
represented | FORM_ANSWER |
case_description | TEXT_ENTERED_BY_CONSUMER |
landing_page_url | https://www.example.com/accident-help |
xxTrustedFormCertUrl | https://cert.trustedform.com/EXAMPLE |
xxTrustedFormPingUrl | https://ping.trustedform.com/EXAMPLE |
tcpa_text | OPT_IN_TEXT_SHOWN_TO_CONSUMER |
user_agent | Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) |
submission_time | 2026-10-01T14:32:10Z |
ip_address | 192.0.2.44 |
xxTrustedFormToken | EXAMPLE |
The same example lead as JSON. Example values. Not a real consumer.
{
"first_name": "Jordan",
"last_name": "Example",
"email": "jordan.example@example.com",
"phone": "555-0142",
"state": "NV",
"zip_code": "89101",
"city": "Las Vegas",
"county": "Clark",
"injury": "FORM_ANSWER",
"at_fault": "FORM_ANSWER",
"accident_type": "FORM_ANSWER",
"accident_date": "2026-09-28",
"doctor_treated": "FORM_ANSWER",
"serious_injury": "FORM_ANSWER",
"represented": "FORM_ANSWER",
"case_description": "TEXT_ENTERED_BY_CONSUMER",
"landing_page_url": "https://www.example.com/accident-help",
"xxTrustedFormCertUrl": "https://cert.trustedform.com/EXAMPLE",
"xxTrustedFormPingUrl": "https://ping.trustedform.com/EXAMPLE",
"tcpa_text": "OPT_IN_TEXT_SHOWN_TO_CONSUMER",
"user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X)",
"submission_time": "2026-10-01T14:32:10Z",
"ip_address": "192.0.2.44",
"xxTrustedFormToken": "EXAMPLE"
}In a live lead, submission_time is the field that shows how old the lead is. Compare it with the time the post reached your system to see how quickly the lead was delivered.
Fields buyers filter on
Filters are configured on our side, per campaign, from the details you send. On car accident leads, buyers most often filterFilterA rule that decides which leads a buyer is offered, based on fields such as vertical, sub-type, state, ZIP code, homeownership or accident details. Glossary on these five fields:
- state (and zip_code): the states, or the ZIP codes inside them, where you or your client take cases. Rules that differ by state, such as filing deadlines and fault rules, are on each state page: see car accident leads by state.
- accident_type: the kinds of accident you accept.
- accident_date: how recent the accident must be. Early contact matters in this vertical, so many buyers set a recency rule.
- doctor_treated: whether the claimant has been treated for the injury, alongside injury and serious_injury.
- represented: claimants who already have an attorney are screened out.
Filtering also happens before a lead is offered at all: Summit’s car accident leads are checked for documented injury, clear or favorable liability, recency, representation, contact data and consent. That quality bar is described on car accident leads.
The consent record on a car accident lead
TCPATCPAThe Telephone Consumer Protection Act, the federal law that governs telemarketing calls and texts, autodialers, prerecorded voice messages and the Do Not Call Registry. Glossary consent is captured on every lead, with consent certificates. On a car accident lead, the consent record fields are tcpa_text (the opt-in language the claimant saw), submission_time, ip_address, user_agent and landing_page_url, plus three TrustedForm fields.
What the TrustedForm fields are
TrustedForm is a third-party service that records a form session and issues a certificate for it. xxTrustedFormCertUrl is the link to that certificate, xxTrustedFormToken is the certificate ID, and xxTrustedFormPingUrl is a second link used to check that the certificate exists before a buyer keeps it. A buyer that keeps the certificate has its own record of the page, the time and the consent language behind the lead.
What the Jornaya field is
Jornaya is another third-party service that records form sessions. Its field, jornaya_leadid, is an ID a buyer can use to look up Jornaya’s record of the submission. It appears on the home service field lists, for example the sample roofing lead, and not on the car accident field list.
For the consent rules behind these records, see TCPA compliance for MVA leads, express written consent and TCPA for ping/post delivery. Law firms that buy these leads should also read personal injury law firms.
This page is general information, not legal advice. Whether a consent record supports the way your firm or your client contacts a claimant is a question for your own counsel.
How a car accident lead is delivered
A car accident lead reaches you in two messages. The ping carries the state, ZIP code and the accident and injury answers, without the claimant’s name, phone number or email address. If your system bids and wins, the post carries the full lead shown above. The message formats, response window and testing steps are in how the ping/post integration works.
Summit currently works with web leads, not calls or live transfers. Leads are exclusive by default, with shared delivery on request, in all U.S. states.
Leads that went through the real-time auction without being sold are a separate product: see overflow MVA leads.
Frequently asked questions
Which accident and injury questions does a car accident lead answer?
Eight: whether the claimant reports an injury, whether they say they were at fault, the accident type, the accident date, whether a doctor treated them, whether they describe the injury as serious, whether they already have a lawyer, and a description in their own words.
Why does the sample car accident lead show FORM_ANSWER instead of answers?
The accident and injury fields are described, not filled with values, so the sample does not suggest which answers a lead will have. The answer formats are set in the field specification shared during onboarding.
How can a buyer tell how old a car accident lead is?
From submission_time, the date and time the claimant submitted the form, together with accident_date for how long ago the accident happened.
Does a car accident lead include a street address?
No. Car accident leads carry the state, ZIP code, city and county. The home service verticals ask for the street address of the property instead.
Related guides
Want the car accident field specification?
Tell us your states, daily caps and delivery method, and we will send the field specification.
Or write to team@summitleads.ai. We reply by email.
What happens next
- Step 1: You email us.
- Step 2: We reply by email.
- Step 3: Return terms are agreed on the onboarding call, before you go live.
Generating leads instead? Sell your leads
Email team@summitleads.ai to become a buyer. summitleads.ai/for-buyers/sample-leads/car-accident