Vendor Posting API — PolicyTek

The one thing that matters

Vendor posts are identical to standard lead posts with one addition: the top-level "redistribute": true. That flag routes your call or lead into the PolicyTek marketplace for redistribution. Without it, nothing redistributes. Do not forget it.

1. Endpoint

POST

https://api.policytek.com/v1/lead/external

JSON body, Content-Type: application/json. Use the API key PolicyTek assigned to you as wsApiToken.

2. Minimum request

JSON · minimum

{
  "wsApiToken": "YOUR_API_KEY",
  "leadData": {
    "phoneNumber": "(555) 555-5555"
  },
  "redistribute": true
}

Only two things are truly required inside the body: a valid phone number and theredistribute flag. Everything else improves match quality.

3. Full example

JSON · full

{
  "wsApiToken": "YOUR_API_KEY",

  "leadData": {
    "firstName": "Alvin",
    "lastName": "Patrick",
    "phoneNumber": "(555) 555-5555",
    "email": "ajpatrick@example.com",

    "birthday": "1957-12-29",
    "address": "852 Vegas Valley Dr",
    "city": "Las Vegas",
    "state": "NV",
    "zipCode": "89109",

    "maritalStatus": "single",
    "smokingStatus": false,

    "height_imperial": "5'10",
    "weight_pounds": 142
  },

  "redistribute": true
}

4. cURL

Shell

curl -X POST https://api.policytek.com/v1/lead/external \
  -H "Content-Type: application/json" \
  -d '{
    "wsApiToken": "YOUR_API_KEY",
    "leadData": {
      "phoneNumber": "(555) 555-5555",
      "firstName": "Alvin",
      "lastName": "Patrick"
    },
    "redistribute": true
  }'

5. Field reference

Field	Type	Required	Notes
`wsApiToken`	string	Required	Your vendor API key from PolicyTek.
`redistribute`	boolean	Required	Must be `true` — a real JSON boolean, not the string `"true"`. Top level, next to `wsApiToken`.
`leadData`	object	Required	Container for the consumer’s information.
`leadData.phoneNumber`	string	Required	Any readable format (e.g. `(555) 555-5555`) or ISO/E.164 (e.g. `+15555555555`). We normalize on our side.
`leadData.firstName`	string	Optional
`leadData.lastName`	string	Optional
`leadData.email`	string	Optional
`leadData.birthday`	string	Optional	Standard date string, e.g. `1957-12-29`.
`leadData.address`	string	Optional	Street address line.
`leadData.city`	string	Optional
`leadData.state`	string	Optional	Two-letter U.S. state code, e.g. `NV`.
`leadData.zipCode`	string	Optional
`leadData.maritalStatus`	string	Optional	Must be lowercase. One of: `single`, `married`, `widowed`.
`leadData.smokingStatus`	boolean	Optional	Send a real boolean — `true` or `false`, not the string `"false"`.
`leadData.height_imperial`	string	Optional	Imperial notation, e.g. `"5’10"`. Use this or `height_ft` or `height`.
`leadData.height_ft`	number	Optional	Height in feet.
`leadData.height`	number	Optional	Height in centimeters.
`leadData.weight_pounds`	number	Optional	Weight in pounds.
`leadData.trackingData`	object	Optional	UTM parameters, Jornaya LeadiD, TrustedForm and your own IDs. See Tracking data.

6. Tracking data

Put attribution and compliance data in leadData.trackingData. It is an object of string keys and values, and every field in it is optional. Common uses:

UTM parameters: utm_source, utm_medium, utm_campaign, utm_content, utm_term.
Jornaya LeadiD: the LeadiD token captured on your form.
TrustedForm: the certificate URL.
Your own IDs, such as a sub ID, click ID or call ID from your system.

JSON · tracking data

{
  "wsApiToken": "YOUR_API_KEY",
  "leadData": {
    "phoneNumber": "(555) 555-5555",

    "trackingData": {
      "utm_source": "facebook",
      "utm_medium": "paid_social",
      "utm_campaign": "final-expense-q4",
      "jornaya_leadid": "YOUR_JORNAYA_LEADID_TOKEN",
      "trustedform_cert_url": "https://cert.trustedform.com/YOUR_CERT_ID",
      "sub_id": "aff-1042"
    }
  },
  "redistribute": true
}

You choose the key names, and we store them exactly as you send them. The names above are suggestions. Whatever names you pick, use the same ones on every post.
Send values as strings. You can leave out any key you don’t have. Empty strings are accepted too.
Any of these keys can go into the postbacks we send you. When we set up your postback, tell us which keys it should include.
Don’t send clickID, hitID, funnelFluxHitId or adParams unless we ask you to. PolicyTek uses those names for its own attribution.

7. Rules

redistribute: true on every post. It is the whole point of this page.
Booleans are real JSON booleans — never quoted strings.
One POST per call or lead, sent in real time as it happens.

8. Need help?

Email contact@policytek.com with your company name and a sample payload; we’ll confirm your integration end to end.