Skip to content

FousNIPR

Get your producers' NIPR licensing data through an API

Read a producer's licenses, lines of authority, appointments and RIRS actions from the NIPR Producer Database with one API call. A workflow can check every producer each Monday and email you the licenses coming up for renewal.

Works with your own NIPR account. Fous is an independent product.

What you can build on NIPR

  • Get a producer's PDB detail report

    Build this

    Runs a detail report in PDB Reports for one NPN and reads its demographic, licensing, appointment and regulatory action (RIRS) sections.

    Takes
    NPN
    Returns
    Name, NPN, resident state, licenses by state with number, class, lines of authority, status and expiration, appointments, RIRS actions
  • Run a batch producer report

    Build this

    Enters a list of NPNs as typed entries in PDB Reports, runs a batch producer report and reads the licensing data for each producer.

    Takes
    List of NPNs
    Returns
    For each NPN: name, resident state, licenses with state, number, class, lines of authority, status and expiration
  • List a licensee's LicenseHub orders

    Build this

    Signs in to LicenseHub as the licensee and reads the dashboard: applications under Incomplete orders and recently submitted ones under Order history.

    Takes
    NPN, last four digits of SSN, date of birth
    Returns
    For each order: list, state, application type, date
  • Start a license renewal application

    Build this

    In LicenseHub, starts a Renewal application for one state, checks the license classes and lines of authority, and leaves it under Incomplete orders unpaid.

    Takes
    NPN, last four digits of SSN, date of birth, state, resident or non-resident
    Returns
    State, license classes, lines of authority, fee summary, where the application was saved

Automate NIPR with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Licenses up for renewal in the next 90 days

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    Run a batch producer report for the NPNs on your producer list.
    Step 2
    Keep the licenses whose expiration date falls in the next 90 days.
    Step 3
    Email you the list, one line per license with producer, state, class and expiration date.
  • New regulatory actions and appointment changes

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    For each NPN on your producer list, get the PDB detail report.
    Step 2
    Keep licenses, appointments and RIRS actions that are new or changed since the last run.
    Step 3
    Post each change, with NPN, state and what changed, to your compliance system's webhook.
  • Renewal applications prepared for review

    Build this
    Starts
    When your system calls the webhook with an NPN, date of birth, SSN last four and a state
    Step 1
    Get the PDB detail report and stop if the license in that state is not active.
    Step 2
    Start the renewal application in LicenseHub and leave it under Incomplete orders.
    Step 3
    Email you the license classes, lines of authority and fee summary to check and pay.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get a producer's PDB detail report” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "pdb.nipr.com/get_pdb_detail_report",
    "input": {
      "npn": "19283746"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "name": "Acme Insurance Agency LLC",
    "npn": "19283746",
    "resident_state": "MO",
    "licenses": [
      {
        "state": "MO",
        "license_number": "8031477",
        "license_class": "Producer",
        "lines_of_authority": "Life, Accident & Health",
        "status": "Active",
        "expiration_date": "2027-02-28"
      }
    ],
    "appointments": [
      {
        "state": "MO",
        "company": "Northwind Life Insurance Company",
        "status": "Active"
      }
    ],
    "regulatory_actions": []
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

NIPR’s own options

NIPR sells Producer Database access as subscriber services: batch producer reports, delivered as PDF or XML, and alerts on appointments, terminations, addresses, licenses and regulatory actions. A company gets them after a PDB access form and a license agreement, invoiced monthly. APIs and the NIPR Gateway are arranged with NIPR's business development team.

OptionWhat it coversWhat it takes
PDB reports and alertsDetail and batch producer reports (CSV or typed entries in, PDF or XML out) and alerts on appointments, terminations, address changes, licenses and RIRS.A subscriber account after the PDB access form and license agreement, with monthly Subscriber Services invoices.
APIs and the NIPR GatewayYour own system connects to NIPR to send appointments and terminations, processed in real time in the SBS states.Arranged through NIPR's business development team. Programming to NIPR's data standards; fees vary by method.
NIPR by handLicenseHub for applications and renewals, one free detail report a year per insurance professional, and PDB Reports for subscribers.State fees plus NIPR's transaction fee, currently $5.60, paid by card or electronic check. Fees are not refunded.

Read on November 12, 2026: NIPR Reports and Alerts, Get help with NIPR subscriber services, NIPR Appointments and terminations.

Signing in to NIPR

PDB Reports asks subscribers for a username and password; your company administrator gives each user a user ID and products and can reset passwords. LicenseHub identifies the licensee by NPN, license number, SSN or FEIN, with date of birth and the last four digits of the SSN. With Fous you sign in once through NIPR's own sign-in: the login is sealed with AES-256 and code and AI agents never see it.

Worth knowing

Renewal keeps the lines you already hold
A renewal can only renew existing lines of authority. Adding a line of authority is a separate application, made after the renewal has processed.
Renewal windows usually open 60 to 120 days out
Windows vary by state and typically open 60 to 120 days before expiration. NIPR suggests finishing CE at least 30 days ahead, since results take 3 to 5 business days to reach the state and NIPR.
Fees are not refunded
Each application carries state fees plus NIPR's transaction fee, currently $5.60, and fees are not refunded. A duplicate application warning means stop and contact NIPR before paying twice.
Each subscriber user has its own user ID
Your company administrator creates user IDs, assigns each user the PDB products they may use and an account for invoicing. A method works with the products your user ID has.

More in Insurance

Other industries: Collaborati, myDSV, Fidelity Wealthscape, ShipmentLink, Opendock, ONE.Konzern Business Plattform.

Frequently asked questions

Yes, by arrangement. NIPR's business development team handles access to its APIs and services, and the NIPR Gateway lets your own system send appointments and terminations. PDB batch reports and alerts are subscriber services after a PDB access form and license agreement, invoiced monthly.

Demographic, licensing, appointment and regulatory action (RIRS) information for one producer. The PDB holds licensing details from all 50 states, the District of Columbia, Guam, Puerto Rico and the U.S. Virgin Islands.

Yes, as a PDB subscriber. Batch producer reports take producer data as a CSV or typed entries and come back as PDF or XML. With Fous, a workflow can run a batch report on a schedule and email you the result or post it to your system by webhook.

Yes. LicenseHub asks for the licensee's identifying details, and NIPR's guide says to enter their information when you work on someone else's behalf. The application also asks who the Authorized Submitter is.

No. Fous is an independent product. You use it with your own NIPR access, and a method reads and does only what that account can.

Put NIPR behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextAflac Business ServicesNational General agent portalTravelers for AgentsCollaboratiHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of NIPR (National Insurance Producer Registry). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.