Integrations

Connect your workspace to the tools, data sources, and model providers you use.

Modernize Integration Reference

Modernize is a publisher-side lead intake partner, not a public contractor-management API. Use this reference when your team needs to send leads into Modernize through the documented ping/post flow.

Do not assume the public Modernize API covers contractor portal functions such as lead history retrieval, budget controls, appointment status, or account analytics.

Public Scope

The supported public flow is Ping/Post v3:

PING checks whether a lead is eligible and can return a price plus pingToken
POST submits the full lead using the returned pingToken
authentication uses tagId in the JSON body
staging uses a documented test tagId
production tag IDs are assigned by Modernize / QuinStreet

Where To Configure It

Open Settings > Integrations, then open Modernize. The integration detail page explains that this is a manual partner integration and gives the team the setup expectations.

Production Endpoints

Operation	URL
`PING`	`https://form-service-hs.qnst.com/ping-post/pings`
`POST`	`https://form-service-hs.qnst.com/ping-post/posts`

Staging Endpoints

Operation	URL
`PING`	`https://hsapiservice.quinstage.com/ping-post/pings`
`POST`	`https://hsapiservice.quinstage.com/ping-post/posts`

Request Rules

send POST requests with Content-Type: application/json
keep field names case-sensitive
use tagId in the payload instead of OAuth or bearer headers
include a compliance token such as trustedFormToken or leadIDToken
validate service-specific fields for the service code you are using
plan around a short timeout budget for lead intake requests

Ping Flow

Common base fields include:

Field	Notes
`tagId`	publisher identifier
`service`	Modernize service code
`postalCode`	consumer ZIP code
`buyTimeframe`	purchase timeline
`ownHome`	home ownership response
`partnerSourceId`	campaign or source identifier
`publisherSubId`	transaction identifier
`trustedFormToken`	TrustedForm certificate URL
`leadIDToken`	Jornaya LeadiD token

Service-specific fields still apply. Confirm them before production launch.

Post Flow

The final POST usually includes the base fields plus:

pingToken
first and last name
email
phone
address, city, and state
TCPA consent language
consent key identifiers

Constraints To Plan Around

the public docs describe publisher intake, not contractor-side account management
production credentials come from Modernize / QuinStreet
service-specific required fields can change
this integration should be validated with Modernize before live traffic

Recommended OzziOs Use

Inside OzziOs, treat Modernize as:

a manual partner reference in Settings > Integrations
endpoint and payload guidance for a lead-intake workflow
a guardrail against promising unsupported contractor-side API capabilities

Sources

Available Integrations & Status