Search
K

ProducerSync API Overview

A producer can only sell where they're licensed and appointed, and that status changes constantly — licenses lapse, appointments are terminated, regulatory actions get filed. Checking each producer by hand doesn't scale, and finding out late creates compliance risk.

ProducerSync gives your systems that compliance picture directly from NIPR (the National Insurance Producer Registry), the industry's system of record, and notifies you when it changes.

What you can get:

  • Licenses and appointments — what a producer can sell, and where
  • Regulatory actions — disciplinary history on file with the states
  • Producer details as the state has them — addresses, contact information, biographical details, and alternative names

ProducerSync vs. Identity: ProducerSync reflects what the state knows about a producer, sourced from NIPR. The Identity API holds what your organization knows — contact info, bank accounts, E&O coverage — which comes from you or the producer directly.

Common Use Cases

Carriers — verify licensing status before appointment, monitor compliance across your distribution network, and track regulatory actions automatically.

Managing General Agents (MGAs) — validate credentials during onboarding and maintain a compliance database synced daily with NIPR.

Technology partners — integrate compliance data into agency management systems or producer portals, build automated compliance checkpoints, and develop regulatory reporting.

How It Works

NPNs

Every insurance producer has a National Producer Number (NPN), a unique identifier issued by NIPR. The NPN is the primary key across every ProducerSync endpoint: you query by NPN, subscribe NPNs for monitoring, and receive webhook events scoped to your NPN population.

Subscriptions and Your Monitored Population

To access data for a producer, you subscribe their NPN to your account. This adds them to your monitored population — the set of NPNs AgentSync actively tracks for your organization.

Subscriptions matter for two reasons:

  • Performance — subscribed NPNs respond at P90 < 1s. Unsubscribed NPNs can take 10s+, as data must be fetched on demand.
  • Webhooks — producersync.updates_available covers your monitored population. It fires once per day, when AgentSync finishes processing NIPR's update across all your NPNs — a single "your data is ready" signal, not a per-producer notification.

Data for a newly subscribed NPN may not be immediately available. It is retrieved from NIPR as your subscription job runs, which can take minutes to a few hours for large batches. Poll the job status endpoint to know when data is ready — see Best Practices.

NIPR Daily Update Cycle

NIPR publishes updated producer data once per day. AgentSync processes it and fires a producersync.updates_available event carrying a runDate. Pass that runDate as the updatedSince query parameter to fetch only changed records — the recommended pattern for efficient daily sync.

NIPR data is not real-time. Newly issued licenses or appointments may not appear until the following day's update cycle.

Two behaviors to plan for when reading collections:

  • includeDeleted defaults to true — NIPR-deleted records are returned unless you opt out. Filter them if your downstream system treats deletion as removal.
  • v1 collection endpoints are deprecated. /v1/licenses, /v1/appointments, and the rest were deprecated in October 2025. Use /v2/ equivalents for all new integrations.

Getting Started

Start here: the ProducerSync API Quick Start Guide covers authentication, subscribing your first NPNs, and setting up the daily sync workflow.

For every endpoint, query parameter, request/response schema, and field detail, see the interactive API Reference.

Customers with Manage

If you haven't purchased the ProducerSync API, you may be looking for Salesforce resources to interact with your Manage instance: