# Fenris API Documentation > Fenris provides insurance prefill and scoring APIs covering Personal Auto, Property, Commercial, Customer Insights, Lead Scoring, and Analytics. The API suite returns pre-filled applicant data and risk scores to streamline quoting and underwriting workflows. All endpoints require OAuth2 bearer token authentication. Fenris APIs are consumed by carriers and MGAs to reduce form-fill friction, validate risk data, and improve conversion rates. Start with the authentication guide to obtain a token, then use the endpoint sections below to select the right API for your use case. ## Core Resources - [Full API Reference](https://documentation.fenrisd.com/.md): Complete reference for all Fenris API endpoint groups — personal auto, property, commercial, customer insights, lead scoring, and analytics — including parameters, request/response schemas, and examples. The interactive HTML explorer with live request trying is also available at the site root. - [Authentication Guide](https://documentation.fenrisd.com/authentication.md): Step-by-step instructions for obtaining OAuth2 bearer tokens. All Fenris API requests require a valid `Authorization: Bearer ` header; tokens expire after 24 hours and must be refreshed. - [OpenAPI Specification (YAML)](https://documentation.fenrisd.com/fenris-api.yaml): Complete OpenAPI 3.1.0 YAML definition for all Fenris endpoints. Use this for SDK generation, Postman imports, automated schema validation, or direct machine consumption without loading the HTML documentation site. - [Postman Collection](https://documenter.getpostman.com/view/53869477/2sBXitBS4b): Ready-to-use Postman requests for all Fenris APIs, pre-loaded with developer data and a pre-request script that handles bearer token refresh automatically. Best starting point for manual testing and exploration. ## API Endpoints by Tag ### Personal Auto Insurance - [Personal Auto Insurance Prefill](https://documentation.fenrisd.com/.md#personal-auto-insurance-prefill): Returns pre-filled auto insurance application data for an individual, including vehicles, prior coverage, and household members. Input: applicant name and address. Use this to populate quote forms; unlike Driver Record Insights, it returns application-level fields rather than violation history. - [Plate to VIN](https://documentation.fenrisd.com/.md#plate-to-vin): Accepts one or more license plate and state pairs and returns vehicle registration data including VIN, make, model, and year. Input: license plate number and two-letter state code (one or more pairs). Use this when you have plate data but not a VIN; NY plates are not supported. - [VIN Decoder](https://documentation.fenrisd.com/.md#vin-decoder): Returns make, model, year, and vehicle specifications for a given VIN. Input: VIN number (GET parameter). Use this when you already have a VIN; simpler and faster than Plate to VIN, which resolves from a plate number. - [Drivers License Lookup](https://documentation.fenrisd.com/.md#drivers-license-lookup): Returns a driver's license number and issuing state for an individual. Input: applicant name and address. Use this to retrieve a license number before requesting violation history via Driver Record Insights. - [Driver Record Insights](https://documentation.fenrisd.com/.md#driver-record-insights): Returns violations and history from a driver's record. Input: address OR driver's license number. Use this for underwriting risk assessment; if you only have a name, call Drivers License Lookup first to obtain the license number. ### Commercial Insurance - [Commercial Prefill](https://documentation.fenrisd.com/.md#commercial-prefill): Returns extensive business details for commercial insurance applications, including industry classification, employee count, revenue, and contact data. Input: business name and address. Use this to pre-populate commercial quote forms. - [Commercial Prefill Financial Information](https://documentation.fenrisd.com/.md#commercial-prefill-financial-information): Returns financial health scores and details for a business, including credit indicators and financial risk signals. Input: business name and address. Use this for financial risk assessment during commercial underwriting; complements Commercial Prefill, which covers general business characteristics rather than financial metrics. ### Property Insurance - [Property - Assessment Details](https://documentation.fenrisd.com/.md#property-assessment-details): Returns building characteristics, assessed valuation, and reported property details such as structure type, lot size, and year built. Input: property address. Use this as the foundational property data layer; covers building attributes, not risk scores or replacement costs. - [Property - Hazards, Perils, Crime](https://documentation.fenrisd.com/.md#property-hazards-perils-crime): Returns a geographic risk assessment covering natural hazards, perils exposure, and crime scores for a property location. Input: property address. Use this for environmental and crime risk scoring; distinct from Assessment Details, which covers building characteristics rather than location-based risk. - [Property - Replacement Cost](https://documentation.fenrisd.com/.md#property-replacement-cost): Returns an estimate of the full building replacement cost including a cost range summary. Input: property address. Use this to set dwelling coverage limits for the entire structure; for roof-only coverage estimates use Property - Roof Replacement Cost. - [Property - Roof Replacement Cost](https://documentation.fenrisd.com/.md#property-roof-replacement-cost): Returns an estimate of the cost to replace a property's roof, including cost range and roof material attributes. Input: property address. Use this for targeted roof coverage assessment; more specific than Replacement Cost, which covers the full structure. ### Customer Insights - [Customer 360](https://documentation.fenrisd.com/.md#customer-360): Returns household and individual demographic information for insurance applications, including contact details and household composition. Input: person name and address. Use this for life and health insurance prefill or any scenario requiring household-level data. - [FenrisProfile+](https://documentation.fenrisd.com/.md#fenrisprofile): Assesses the quality and validity of contact information from internet leads, detecting typos and intentionally false submissions. Input: name, email, phone, and address. Use this to validate lead data before investing in a full prefill or scoring request. ### Scoring & Analytics - [Lead Insights](https://documentation.fenrisd.com/.md#lead-insights): Scores an insurance lead across auto, home, commercial, life, or health lines using a specified model type such as returnlikelihood, sellability, or quotability. Input: applicant data, line of business (auto/home/commercial/life/health), and model type. Use this to prioritize leads before running a full prefill. - [Applicant Insights](https://documentation.fenrisd.com/.md#applicant-insights): Returns a risk score for an individual applicant given a line of business and product line. Input: person name, address, outcome type, line of business, and product line. Use this for individual risk scoring; the commercial equivalent is Commercial Scores. - [Commercial Scores](https://documentation.fenrisd.com/.md#commercial-scores): Returns a risk score for a business given a line of business and product line. Input: business data, outcome type, line of business, and product line. Use this for commercial risk scoring; the personal equivalent is Applicant Insights. ### Outcomes - [Outcome Service](https://documentation.fenrisd.com/.md#outcome-service): Submits an actual outcome back to Fenris after a score or prefill request has been acted on. Input: a requestId from a prior Fenris response plus the observed outcome. Use this to close the feedback loop and support ongoing model improvement. ### Developer Resources - [Authentication](https://documentation.fenrisd.com/.md#authentication): Overview of the OAuth2 bearer token authentication scheme used by all Fenris APIs, including how to request credentials and how long tokens remain valid (24 hours). - [Developer Data](https://documentation.fenrisd.com/.md#developer-data): Links to downloadable synthetic test data sets for personal, business, and Plate to VIN scenarios. Requests made with developer data return constant, guaranteed responses and are never billed to your account. - [Postman](https://documentation.fenrisd.com/.md#postman): Setup guide for the Fenris Postman collection, including environment variable configuration for client credentials and how the pre-request script manages automatic token refresh before each request. - [Making a Request](https://documentation.fenrisd.com/.md#making-a-request): Overview of REST conventions used by Fenris APIs, including when to use GET vs POST, required headers, and the optional `submission-id` header for correlating Fenris responses with your internal tracking systems. - [Echo Service](https://documentation.fenrisd.com/.md#echo-service): Echoes any message sent to it with no side effects. Use this to verify that authentication and network connectivity are working correctly before making production requests.