Table of Contents
Support Guide
Lead Posting Array Data into Shape's Insurance Template
-
Chloe Larson
Learn how to post array data into Shape's Insurance template, including multiple drivers, vehicles, properties, coverages, and incidents within a single lead using Shape's Lead Posting API.
Lead Posting Array Data into Shape's Insurance Template
Insurance leads are often much more complex than a traditional contact record.
A single customer may have:
- Multiple drivers
- Multiple vehicles
- Multiple properties
- Multiple insurance policies
- Multiple coverages
- Multiple incidents
Rather than creating separate records for each item, Shape allows you to post these related objects as arrays within a single API request. This keeps all of the customer's insurance information organized under one record while preserving the relationships between each object.
When Should I Use Array Posting?
Use array posting anytime your lead provider or integration needs to submit multiple instances of the same type of information.
Common examples include:
- Two or more drivers
- Multiple vehicles
- Multiple insured properties
- Several insurance coverages
- Multiple driving incidents
- Additional insurance-related objects supported by your template
Instead of sending several POST requests, everything can be submitted together in a single payload.
Supported Insurance Objects
Depending on your implementation, Shape supports posting arrays for insurance-specific objects,
Such as:
- Drivers
- Vehicles
- Properties
- Coverages
- Driving Incidents
Each object becomes associated with the same primary contact record.
Creating Your Lead Posting URL
Before posting data into Shape, you'll need a Marketing Source with a Lead Posting URL.
Step 1
Navigate to:
Settings → Marketing Sources
Step 2
Locate your existing Marketing Source.
If one already exists, simply use the Lead Posting URL generated by Shape.
Step 3
Need a new source?
Select Add Source.
Configure:
- Source Name
- Record Type = Leads
After saving, Shape automatically generates your unique Lead Posting URL.
Mapping Your Fields
Every Marketing Source includes a list of supported field mappings.
When posting data:
- Use the Field Name exactly as shown.
- Field names are case-sensitive.
- Unsupported or incorrectly named fields are not discarded. Instead, they're appended to the Notes section of the record for reference.
This makes troubleshooting much easier while helping identify mapping issues.
For a complete list of supported fields, refer to the Supported Field Reference.
Building Your Payload
Your payload contains two types of data:
Primary Contact Information
Information about the insured individual.
Examples include:
- First Name
- Last Name
- Phone Number
Related Objects
Additional information is submitted as arrays beneath the primary contact.
Examples include:
None
Lead
├── Drivers[] ├── Vehicles[] ├── Properties[] └── Policies / Coverages[]
Each array can contain one or many objects depending on the customer's information.
Each array can contain one or many objects depending on the customer's information. This structure allows one Shape record to represent an entire insurance profile.
Example Payload
None
Screenshot / Code Placeholder
(Keep your existing JSON example here.)
Successful Response
If your request is successful, Shape returns a response similar to:
None
{
"status": 1,
"msg": "success",
"leadId": 1818,
"systemId": 16638
}
The returned Lead ID uniquely identifies the record that was created.
You can search for this Lead ID inside Shape to verify your mappings and imported data.
Troubleshooting
If information doesn't appear where expected, check the following:
- Verify every field name matches Shape exactly.
- Confirm you're posting to the correct Marketing Source.
- Validate that array objects are formatted correctly.
- Ensure nested objects (such as Coverages within Vehicles) follow the expected structure.
- Review the Notes section of the created record for unsupported field names.
Best Practices
- Submit one customer per request.
- Keep related insurance objects within the same payload.
- Use Shape's published field names exactly as documented.
- Test using a dedicated Marketing Source before deploying to production.
- Search using the returned Lead ID to verify successful imports.
Frequently Asked Questions
When should I use array posting?
Array posting should be used whenever a customer has multiple related insurance objects, such as several vehicles, drivers, or properties that belong to the same record.
Can I post multiple vehicles on the same lead?
Yes. Vehicles are submitted as an array, allowing a single lead to contain as many vehicles as needed.
Can I submit multiple drivers?
Yes. Driver information can be posted as an array, allowing multiple insured drivers to be associated with the same customer record.
What happens if I use the wrong field name?
Unsupported or incorrectly named fields are automatically added to the record's Notes section instead of being mapped to a field.
Do I need to match Shape's dropdown values?
Yes. When posting to dropdown or predefined list fields, the submitted values should match the options configured in your Shape template.
How do I know my POST was successful?
A successful response returns a status, Lead ID, and System ID. You can search for the returned Lead ID in Shape to verify that your data imported correctly.
Can Shape help me configure my Marketing Source?
Yes. If you need assistance configuring a Marketing Source or troubleshooting your integration, contact help@setshape.com and include:
- Your full request payload
- Request headers
- Query parameters (if applicable)
- Any returned error messages
This information helps our team troubleshoot your integration more efficiently.
Keywords: Marketing Source, Array, Post URL, Field Name, Friendly Name, Insurance, Everquote, QuoteWizard, lead provider, multiple objects, API
