Product Access Requirements
Some products — including state Electronic Vehicle Title & Registration and Motor Vehicle Record inquiry APIs — carry additional state program requirements. These are separate from the OAuth credentials required for all API access — they're each state's own rules for who may use the system and how. Before requesting Stage or Production access, confirm your organization can meet that state's program requirements in the Access Requirements matrix below.
Access Requirements
Each column below answers one question about that state's requirements. An answer of Depends means the requirement varies by user role or service type — see that cell's detail.
- User Approval — does the state need to approve individual users before they get access?
- Background Check — does the state require background checks for users before access?
- In-State Location — does the company need a brick-and-mortar location in the state?
- On-Site Processing — does processing need to happen at that in-state location?
- Training — do users need training before they get system access?
- Recertification — is recurring / refresher training required?
- License(s) — are any licenses required?
| State | API Product | User Approval | Background Check | In-State Location | On-Site Processing | Training | Recertification | License(s) |
|---|---|---|---|---|---|---|---|---|
| California | California (CA) EVR API | Yes — Required to process transactions. | Yes — Required for users processing transactions. | Yes — Off-site e-filing allowed with state approval. | Yes | Yes | Yes | Yes — Occupational License, BPA Permit, Dealer License. |
| Colorado | Colorado (CO) EVR API | No | Yes | No | No | Yes | No | Yes — Colorado dealer number (CO Dealer#). |
| Florida | Florida (FL) EVR API | No | Yes — Dealer handles it; provides Vitu a signed affidavit confirming completion. | Yes | No — Title work can be processed off-site; indicia cannot leave state lines. | Yes | No | Yes — FL Dealer's License (or authorized insurer / vehicle auction). |
| Idaho | Idaho (ID) EVR API | No | No | Yes | No | Yes | No | Yes — Idaho Dealer's License. |
| Illinois | Illinois (IL) EVR API | No | No | Yes | No | No | No | Yes — Dealer/remitter must obtain proper state licensing before processing. |
| Kentucky | Kentucky (KY) EVR API | Yes — Must apply and be approved through KYELT (the state) before access is granted. | No | Yes | No | No | No | Yes — Kentucky Motor Vehicle Commission. |
| Maryland | Maryland (MD) EVR API | Yes — MVA User Affidavit form + copy of user's driver license, MVA-approved. | No | Yes — No remote-only option today; MVA will permit DTC/central fulfillment on application. | No | No | Yes — Every 6 months. | Yes — Issued by Maryland Dept. of Transportation (MVA). |
| Massachusetts | Massachusetts (MA) EVR API | No — Client/organization is approved, not individual users. | Yes — Tied to the state the user resides in, plus a driving-record check in some cases. | Yes — A location within 50 miles of the border is allowed as a secondary site. | No — Transaction can start at the MA site and be submitted from the approved border-area site. | Yes — 2-day RMV online class + 1-day Dealertrack online class. | No | Yes |
| Minnesota | Minnesota (MN) EVR API | Yes — Title Clerks must pass the MADA title-cert class; other users don't need approval. | No | No — MN dealers (and WI/IA/SD/ND dealers) can house inventory without an in-state requirement. | No — Can title for multiple locations; only actively works at one. | Depends — Certain user roles must complete training/certification; others do not. | Depends — Certain user roles must renew certification every 3 years; others do not. | Yes — MN Dealer number. |
| North Carolina | North Carolina (NC) EVR API | Yes | No | Yes | Yes | Yes — Mandatory 24-hour title clerk training course. | No | Yes — NC Dealer License, issued by NC DMV. |
| Oregon | Oregon (OR) EVR API | No | No | Yes | No | Yes — RMP course, with full onsite access. | No | Yes — Oregon Dealer License, must be 6+ months old. |
| South Carolina | South Carolina (SC) EVR API | No | No | Yes | No | No | No | Yes |
| Texas | Texas (TX) EVR API | No | No | No | Yes | Yes | No | Yes — A dealer must get their GDN (i.e. P-number) from the county prior to utilizing webDEALER for title & reg transactions. |
| Virginia | Virginia (VA) EVR API | No | No | Yes | No — Can process off-site without keeping inventory there. | Yes | Yes | Yes — Issued by the Motor Vehicle Dealer Board (MVDB); VA DMV-approved. |
| Wisconsin | Wisconsin (WI) EVR API | Yes | No | No | No | Yes — Via WAMS (WI's identity/access system). Transitioning to MyWisconsinID in Fall 2026. | Yes — Every 3 years, via WAMS/MyWisconsinID. | Yes |
Requirements are set by each state and can change. Confirm current status with your Vitu account team before relying on this page for a go-live plan.