Section 12: Vehicle Registration Transactions

From Nlets Wiki
Jump to: navigation, search

Vehicle Registration Transactions (RQ/RR, RQG & RNQ/RNR)

This section describes how to access out-of-state vehicle registration information (plate number, license type, license year, VIN, vehicle model, vehicle style, and vehicle color) by sending a query through Nlets to a state or multi-state region by License Plate/Year/Type, VIN, or Name.

Canadian vehicle registration queries are described in "Communicating with Canada".

Mexican vehicle registration queries are described in "Communicating with Mexico".

This section provides an overview and details regarding the Vehicle Registration Query by License Plate/Year/Type, or VIN to a state (RQ), the corresponding Vehicle Registration Response (RR), the Vehicle Registration Query by License Plate/Year/Type, or VIN to a region (RQG), the corresponding Vehicle Registration Response (RR), the Vehicle Registration Query by Name (RNQ), and the corresponding Vehicle Registration Response (RR).

Multi-State Query Functionality

Nlets supports the Multi-State Query functionality for the RQ message format. This functionality allows the query to be automatically sent to all states that participate in the message type and returns a single merged response.

In order to send a Vehicle Registration using the Multi-State Query, the query should be sent in its typical format to the destination NL. Nlets will take this query and send it to ALL states that support the RQ message key. Nlets then collects all relevant responses to this query, merges them together while suppressing the NO HIT responses, and sends them onto the querying user as a single response. These responses will also contain summary data indicating which states this query was sent to, which states responded with hits, which responded with no hits, and which states did not respond at all.

States receiving legacy text or GJXDM formats will see the summary data and state responses in a flattened text format (wrapped in XML for GJXDM), whereas states receiving responses in NIEM will receive the summary and state responses in a standardized XML structure detailed below.

An important detail to note is that if a response is received after Nlets has forwarded on the merged Multi-State response, the late response will be sent individually to the original user. This would be most likely to occur if a participating state happened to be 'down' at the time of the query but came back up at a later time and responded.

Overview

To send a Vehicle Registration Query (RQ/RQG), a user must enter the License Plate, License Year, and License Type (See "Query by License Plate/Year/Type" below), or VIN, Vehicle Make (optional), and Vehicle Manufacture Year (optional) (See "Query by VIN" below).

Positive Vehicle Registration Responses (RR) may contain information including the license number, license type, license year, VIN, vehicle model, vehicle style, and vehicle color for up to two vehicle matches (See "Vehicle Registration Response" below).

Section12-RQ.jpg

Other possible responses to a query include:

  • NOT ON FILE
  • FILE NOT AVAILABLE
  • TEMPORARILY UNAVAILABLE

Query Requirements

  • Each Registration Query (RQ/RQG) can be sent to up to five state or regional codes.
  • A destination code of "Z1" will result in the Query being directed to all states (sends a separate response for each state).
  • A destination code of "NL" will result in the Query being directed to all states (sends a single response for all states).
  • Any indicators or flags from a state DMV file that depict a vehicle record as stolen must be suppressed from interstate transmission over Nlets.
  • To access information on diplomatic plates use the 2-character code "US".
  • To access information on GSA plates use the 2-character code "GS".

Query Help

  • Utilize the states help file for additional DMV ORI information.
  • To obtain explanatory or supplementary information on a state's vehicle registration files, a user may send an Administrative Message to xxLICHELP (where xx = 2 character state code).
  • A user also may determine who is providing automated responses to registration queries and who has a HELP file by sending an Administrative Message to "NLLICHELP".
  • If a complete date of birth is unknown some states support inquiries on age. Consult state vehicle registration HELP file for details. The address is xxLICHELP (where xx=2 character state code).
  • A Help file about GSA can be obtained by sending an Administrative message to GSADMHELP.
  • A Help file about data returned from GSA can be obtained by sending an Administrative message to GSLICHELP.

More information on help files can be located in Help File Transactions.

Data Codes
  • Codes used as input and/or output in the vehicle registration query/response generally match NCIC formats and content. Please refer to Part II of your NCIC Manual for code translation and instruction.
  • If a state cannot conform to the NCIC codes with regard to vehicle make and vehicle model, an easily understandable notation may be substituted.
Vehicle Registration Query Field Requirements (RQ/RQG)

The table that follows describes requirements for Vehicle Registration Queries (RQ/RQG).

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
nc:IdentificationID
LIC/ 1-10 Alphanumeric
only

License
number

nc:IdentificationCategoryText
LIT/ 2-4 See NCIC
Manual

License type

nc:Year
LIY/ 10 ccyy

ccyy, License
year or NX,
Non-expiring

nc:IdentificationID
VIN/ 1-20 Alphanumeric
only

Vehicle
identification
number

nc:VehicleMakeCode
VMA/ 2-4 See NCIC
Manual

Vehicle make

nc:ItemModelYearDate
VYR/ 2-4 See NCIC
Manual

Vehicle model
year date

Registration Name Query/Registration Name Response (RNQ/RNR)

This section provides an overview and details regarding the RNQ/RNR (query by name and its response).

Overview

To send a Vehicle Registration Query (RNQ), a user must enter the Name, Date of Birth (optional), and Age (optional) (See "Name Query" below).

Positive Vehicle Registration Reponses (RNR) may contain information including the License Number, License Type, License Year, VIN, Vehicle Model, Vehicle Style, and Vehicle Color for up to two vehicle matches (See Response below).

Section12-RQ2.jpg

The other possible vehicle registration responses include:

  • FILE NOT AVAILABLE
  • NOT ON FILE
  • TEMPORARILY UNAVAILABLE

Query Requirements

  • Each Registration Query (RNQ) can be sent to no more than one state.
  • To access information on diplomatic plates use the 2-character code "US".
Data Codes
  • Codes used as input and/or output in the vehicle registration query/response generally match NCIC formats and content. Please refer to Part II of your NCIC Manual for code translation and instruction.
  • If a state cannot conform to the NCIC codes with regard to vehicle make and vehicle model, an easily understandable notation may be substituted.
Vehicle Registration by Name Field Requirements (RNQ)

The table below describes requirements for Registration by Name Queries.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
nc:PersonFullName
NAM/ 1-30

Alpha Characters

Person Name: This field
must include at least a
first and last name in the
standard name format
(surname, first name).
Some states allow a
question mark "?" in the
surname if the full
surname is not known.
Consult state help files to
determine if a state can
support this capability.
(E.g., NAM/PUBL?,JOHN Q.)

nc:Date
DOB/ 8

ccyy-mm-dd
See NCIC
Manual

Date of Birth. This field,
if used, must include the
complete date of birth.

nc:PersonAgeDescriptionText
AGE/ 2

Numeric

Age. If a complete
date of birth is unknown,
some states support
inquiries on age. Consult
state vehicle registration
HELP file for details. The
address is xxLICHELP where
xx=2 character state code.

Vehicle Registration Name Field Requirements (RNR)

The RNR Field Requirements are identical to the RR Field Requirements.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

Vehicle Registration NIEM Specifications

This section provides NIEM format and examples for Vehicle Registration Query by License Plate/Year/Type, or VIN to a state (RQ) or region (RQG), and the corresponding Vehicle Registration Response (RR).

Canadian vehicle registration queries are described in "Communicating with Canada".

Mexican vehicle registration queries are described in "Communicating with Mexico".

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Vehicle Registration Query by License Plate, Year, Type (RQ,RQG), Vehicle Registration Query by VIN (RQ,RQG), Vehicle Registration Query by Name (RNQ), Vehicle Registration Response in Free Text (RR) and Standardized Vehicle Registration Response (RR).

Query Formats

Vehicle Registration Query by License Plate, Year, Type (RQ,RQG)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over
  land.

    nc:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the license plate number to be queried

      nc:IdentificationCategoryText
      A kind of identification.
      This element should contain the type of license plate being queried. Allowable values come
      from the NCIC LIT code table.

      nc:IdentificationExpirationDate
      A date after which an identification is no longer valid.

        nc:Year
        A year.
        This element's value should be the expiration date of the license plate, also known as the
        plate year. The value should be in the format YYYY. For non-expiring plates NX or YYYY may
        be entered.

  n2:HistoryRequestIndicator
  This optional element can be used to indicate that a registration history is requested, if
  available. The element will only be passed onto XML states and will be stripped from queries to
  legacy states. Value should be boolean.

Vehicle Registration Query by VIN (RQ,RQG)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over
  land.

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

    nc:VehicleMakeCode
    A manufacturer of a vehicle.
    This optional element will contain the make of the vehicle being queried. Allowable values come
    from the NCIC VMA code table.

    nc:ItemModelYearDate
    A year in which an item was manufactured or produced.
    This element will contain the year of the vehicle. Data should be formatted YYYY.

  n2:HistoryRequestIndicator
  This optional element can be used to indicate that a registration history is requested, if available.
  The element will only be passed onto XML states and will be stripped from queries to legacy
  states. Value should be boolean.

Vehicle Registration Query by Name (RNQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Person
  This element encapsulates the information about the person being queried

    nc:PersonAgeDescriptionText
    A description of the age of a person.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This element contains the DOB for the person being queried on. This data in this element must
      be in xsd:date format, that is: yyyy-mm-dd.

    nc:PersonName
    A combination of names and/or titles by which a person is known.

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but
      will only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST
      MIDDLE. The data from this element is the only name data that will be passed onto states
      receiving text.

Response Formats

Vehicle Registration Response in Free Text (RR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Response Text (n2:ResponseText)


  This element will contain the free text vehicle registration response. Nlets recommends the use of

<nh2:DocumentControlFieldText><![CDATA[NL0000TEST]]></nh2:DocumentControlFieldText>

tags to ensure that the response does not contain any characters illegal in XML.

Standardized Vehicle Registration Status Response (RR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Vehicle Registration Status (nrs2:RegistrationStatus)
  This element will contain the standardized driver status response as defined in the Collaboration
  of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Standardized Vehicle Registration History Response (RR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Vehicle Registration History (nrh2:RegistrationHistory)
  This element will contain the standardized driver history response as defined in the Collaboration
  of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Vehicle Registration NIEM Examples

Example 1: A Vehicle Registration query by license plate, year and type.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>P4</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:57</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:57</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00010</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RQ">
    <nc:Vehicle>
      <nc:ConveyanceRegistrationPlateIdentification>
        <nc:IdentificationID>ABC123</nc:IdentificationID>
        <nc:IdentificationCategoryText>PC</nc:IdentificationCategoryText>
        <nc:IdentificationExpirationDate>
          <nc:Year>2019</nc:Year>
        </nc:IdentificationExpirationDate>
      </nc:ConveyanceRegistrationPlateIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: A Vehicle Registration query by VIN.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>P4</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE2]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:58</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:58</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00011</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>AAAAA11A11A111111</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 3: A Vehicle Registration response.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>CALIC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:59</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:59</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>01183</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="RR">
    <n2:ResponseText>DATE: 10/22/19 TIME: 13:59

INSURANCE INFORMATION UNKNOWN              
REG VALID FROM: 01/26/01 TO 01/26/02
LIC#: abc123 YRMD:71 MAKE:CHEV BTM :PU VIN :VEHICLEIDNUMBER 
R/O :SMITH JOHN, PO BOX 932336 CITY:SACRAMENTO C.C.:34 
ZIP#:94000 
SOLD:01/20/71 RCID:05/20/79 OCID:05/02/79 LOCD:G 

RELEASE OF LIABILITY (REG. 138)
RECEIPT DATE:07/04/96  TRANSFER DATE:07/01/96  SELL PRICE:001500
BUYER:SMITH JOHN, 1234 FAKE AVE 
CITY:SACRAMENTO   SELLER:SAME AS R/O ON FILE    

RELEASE OF LIABILITY (REG. 138)
RECEIPT DATE:11/08/11  TRANSFER DATE:11/01/11  SELL PRICE:000700
BUYER:SMITH JOHN, 1234 FAKE AVE 

CITY:SACRAMENTO CA   SELLER:SAME AS R/O ON FILE    

FEDERAL, STATE OR LOCAL LAW ENFORCEMENT AGENCIES SHALL NOT USE ANY 
NON-CRIMINAL HISTORY INFORMATION CONTAINED WITHIN THIS DATABASE FOR 
IMMIGRATION ENFORCEMENT PURPOSES. THIS RESTRICTION DOES NOT PERTAIN 
TO ANY INFORMATION THAT IS REGARDING A PERSON'S IMMIGRATION OR 
CITIZENSHIP STATUS PURSUANT TO 8 U.S.C 1373 AND 1644

END 
 </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 4: A Vehicle Registration query by Region. The response will be a standard Vehicle Registration response (RR).

<n2:NLETS xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" 
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RQG</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>A1</nh2:DestinationORIID>
    <nh2:DestinationORIID>B1</nh2:DestinationORIID>
    <nh2:DestinationORIID>C1</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CRO55F1R31]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>AAAAA11A11A111111</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 5: A Vehicle Registration query by name.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RNQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>P4</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[RNQEXAMPLE]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>14:06</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>14:06</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00019</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RNQ">
    <nc:Person>
      <nc:PersonName>
        <nc:PersonFullName>SMITH, JOHN</nc:PersonFullName>
      </nc:PersonName>
    </nc:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 6: A Vehicle Registration response by name.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>RNR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>UTBCI0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[RNQEXAMPLE]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>14:09</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>14:09</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>01210</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RNQ">
    <nc2:Vehicle xmlns:nc2="http://www.nlets.org/niem/nlets-core/1.0">
      <nc:VehicleIdentification />
      <nc:ConveyanceRegistration>
        <nc:ConveyanceRegistrationPlateIdentification />
      </nc:ConveyanceRegistration>
    </nc2:Vehicle>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="RNR">
    <nrm2:RegistrationMatch xmlns:nrm2="http://www.nlets.org/niem/nlets-registration-match/1.0">
      <nrm2:IndividualMatch>
        <nc:ConveyanceRegistration>
          <nc:RegistrationExpirationDate />
          <nc2:RegistrationHolder xmlns:nc2="http://www.nlets.org/niem/nlets-core/1.0">
            <nc:EntityOrganization />
            <nc:ContactMailingAddress>
              <nc:StructuredAddress>
                <nc:LocationStreet>
                  <nc:StreetFullText>123 FAKE LN</nc:StreetFullText>
                </nc:LocationStreet>
                <nc:LocationCityName>SLC</nc:LocationCityName>
                <nc:LocationStateName>UT</nc:LocationStateName>
                <nc:LocationCountryName>USA</nc:LocationCountryName>
                <nc:LocationPostalCode>841349000</nc:LocationPostalCode>
              </nc:StructuredAddress>
            </nc:ContactMailingAddress>
            <nc2:Person>
              <nc:PersonBirthDate />
              <nc:PersonName>
                <nc:PersonGivenName>JOHN</nc:PersonGivenName>
                <nc:PersonSurName>SMITH</nc:PersonSurName>
              </nc:PersonName>
            </nc2:Person>
          </nc2:RegistrationHolder>
          <nc:ConveyanceRegistrationPlateIdentification>
            <nc:IdentificationID></nc:IdentificationID>
          </nc:ConveyanceRegistrationPlateIdentification>
        </nc:ConveyanceRegistration>
        <nc:Vehicle>
          <nc:ItemModelYearDate>2010</nc:ItemModelYearDate>
          <nc:VehicleIdentification>
            <nc:IdentificationID>123456789</nc:IdentificationID>
          </nc:VehicleIdentification>
          <nc:VehicleMakeCode>VOLKSWAGEN</nc:VehicleMakeCode>
        </nc:Vehicle>
      </nrm2:IndividualMatch>
      <nrm2:IndividualMatch>
        <nc:ConveyanceRegistration>
          <nc:RegistrationExpirationDate />
          <nc2:RegistrationHolder xmlns:nc2="http://www.nlets.org/niem/nlets-core/1.0">
            <nc:EntityOrganization />
            <nc:ContactMailingAddress>
              <nc:StructuredAddress>
                <nc:LocationStreet>
                  <nc:StreetFullText>123 FAKE LN</nc:StreetFullText>
                </nc:LocationStreet>
                <nc:LocationCityName>OGDEN</nc:LocationCityName>
                <nc:LocationStateName>UT</nc:LocationStateName>
                <nc:LocationCountryName>USA</nc:LocationCountryName>
                <nc:LocationPostalCode>840780000</nc:LocationPostalCode>
              </nc:StructuredAddress>
            </nc:ContactMailingAddress>
            <nc2:Person>
              <nc:PersonBirthDate />
              <nc:PersonName>
                <nc:PersonGivenName>JOHN</nc:PersonGivenName>
                <nc:PersonSurName>SMITH</nc:PersonSurName>
              </nc:PersonName>
            </nc2:Person>
          </nc2:RegistrationHolder>
          <nc:ConveyanceRegistrationPlateIdentification>
            <nc:IdentificationID>123456789</nc:IdentificationID>
          </nc:ConveyanceRegistrationPlateIdentification>
        </nc:ConveyanceRegistration>
        <nc:Vehicle>
          <nc:ItemModelYearDate>2016</nc:ItemModelYearDate>
          <nc:VehicleIdentification>
            <nc:IdentificationID>16VDX16XXXXXXXXXX</nc:IdentificationID>
          </nc:VehicleIdentification>
          <nc:VehicleMakeCode>HARLEY DAVIDSON</nc:VehicleMakeCode>
        </nc:Vehicle>
      </nrm2:IndividualMatch>
    </nrm2:RegistrationMatch>
  </n2:NLETSResponseData>
</n2:NLETS>

Parsed Vehicle Registration NIEM Specifications

This section provides NIEM format and examples for Parsed Vehicle Registration Response to a state (PRR),

Nlets now provides the option for users to receive fully tagged NIEM formatted Registration Responses from all states via our message parsing service. RRs destined to an individual terminal or an entire state can be redirected to the message parsing service to be converted to a Parsed Registration Response (PRR).

The Parsed Registration Response is structured similarly to a standard Registration Response with the addition of some parsing-related elements and the removal of some cardinalities and enumerations.

The parsing service can be setup to parse all statewide RRs or to parse RRs for any number of individual ORIs.

To leverage this service or for more information, contact the Nlets Control Center at 1-800-528-4020.

Benefits and Potential

This parsing technology has a number of real-world benefits. For members, parsed registration responses enable switch vendors to convert the fully tagged XML into a simple, human-readable format. Standardized responses also enable states to create advanced technological policies and procedures based on the data.

Nlets Strategic Partners can also benefit from this parsed data. A number of traffic enforcement strategic partners already maintain their own parsers for the 45 states that return registration responses in unstructured text. This new technology eliminates that time-consuming process and enables our partners to focus their energy on developing and maintaining technology that supports law enforcement.


Element Dictionary

Transaction types detailed below include: Standardized Parsed Vehicle Registration Response (PRR) and Standardized Parsed List Response (PRR).

Response Formats

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Standardized Parsed Vehicle Registration Status Response (PRR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  QualityCommentText (nc:QualityCommentText)
  This element will contain notes on any issue encountered during the parsing of the Text Response.
  An example of some of the issues that might be encountered and notated here include:
  An indication that the original response could only be partially parsed.
  An indication that the original response could not be parsed.
  An indication that the original response contains content that is not part of the CANDLE RR specification.
  In this case, it will also include a note to reference the OriginalTextResponse for additional information.

  OriginalTextResponse (n2:OriginalTextResponse)
  This element will contain the original, unaltered, text response from the incoming RR. If any issues
  were encountered during the parsing of the original text response, you can refer to this element for any
  additional information. Content in the original text response that is outside of the scope of a standard
  CANDLE RR specification will not be parsed and only be located in this element.

  Vehicle Registration Status (nrs2:RegistrationStatus)
  This element will contain the standardized Registration status response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Standardized Parsed Vehicle Registration Match List Response (PRR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  QualityCommentText (nc:QualityCommentText)
  This element will contain notes on any issue encountered during the parsing of the Text Response.

  OriginalTextResponse (n2:OriginalTextResponse)
  This element will contain the original, unaltered, text response from the incoming RR.

  Registration Matches (nrm2:RegistrationMatch)
  This element will contain the standardized Registration match list response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.


Parsed Vehicle Registration NIEM Examples

Example 1: A Parsed Vehicle Registration Status Response.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>PRR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZ007C100</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[PRREXAMPLE]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>14:19</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>14:19</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>01226</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="RQ">
    <n2c:Vehicle xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
      <n2c:ConveyanceRegistrationPlateIdentification>
        <IdentificationExpirationDate xmlns="http://release.niem.gov/niem/niem-core/4.0/">
          <n2:DateText>2015</n2:DateText>
        </IdentificationExpirationDate>
        <IdentificationID xmlns="http://release.niem.gov/niem/niem-core/4.0/">ABC###</IdentificationID>
        <IdentificationCategoryText xmlns="http://release.niem.gov/niem/niem-core/4.0/">PC</IdentificationCategoryText>
      </n2c:ConveyanceRegistrationPlateIdentification>
    </n2c:Vehicle>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="PRR">
    <nrs2:RegistrationStatus xmlns:nrs2="http://www.nlets.org/niem/nlets-registration-status/1.0">
      <n2c:AdditionalInformation xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
        <n2c:StateElement>
          <n2c:ElementFieldName>MESSAGES1</n2c:ElementFieldName>
          <n2c:ElementFieldValue> PLATES NOT VALID FOR HIGHWAY USE</n2c:ElementFieldValue>
        </n2c:StateElement>
        <n2c:StateElement>
          <n2c:ElementFieldName>MESSAGES2</n2c:ElementFieldName>
          <n2c:ElementFieldValue> PLATE IS FOR CREDIT ONLY PREVIOUS VEH INFO BELOW</n2c:ElementFieldValue>
        </n2c:StateElement>
      </n2c:AdditionalInformation>
      <nrs2:StandardResponse>
        <n2c:Vehicle xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:ItemModelYearDate>2000</nc:ItemModelYearDate>
          <nc:PropertyStyleText>4DSD</nc:PropertyStyleText>
          <nc:VehicleMakeCode>TOYT</nc:VehicleMakeCode>
          <nc:VehicleIdentification>
            <nc:IdentificationID>12345678912752545</nc:IdentificationID>
          </nc:VehicleIdentification>
          <nc:ConveyanceRegistration>
            <nc:RegistrationExpirationDate>
              <nc:Date>2017-08-31</nc:Date>
            </nc:RegistrationExpirationDate>
            <n2c:RegistrationHolder>
              <nc:ContactMailingAddress>
                <nc:StructuredAddress>
                  <nc:LocationStreet>
                    <nc:StreetFullText>123 FAKE LN APT 20B</nc:StreetFullText>
                  </nc:LocationStreet>
                  <nc:LocationCityName>TEMPE</nc:LocationCityName>
                  <nc:LocationStateName>AZ</nc:LocationStateName>
                  <nc:LocationPostalCode>852827036</nc:LocationPostalCode>
                </nc:StructuredAddress>
              </nc:ContactMailingAddress>
              <n2c:Person>
                <nc:PersonName>
                  <nc:PersonFullName>SMITH,W,JOHN</nc:PersonFullName>
                </nc:PersonName>
                <nc:DriverLicense>
                  <nc:DriverLicenseIdentification>
                    <nc:IdentificationID>D0#######</nc:IdentificationID>
                  </nc:DriverLicenseIdentification>
                </nc:DriverLicense>
              </n2c:Person>
            </n2c:RegistrationHolder>
            <nc:ConveyanceRegistrationPlateIdentification>
              <nc:IdentificationID>ABC###</nc:IdentificationID>
            </nc:ConveyanceRegistrationPlateIdentification>
          </nc:ConveyanceRegistration>
        </n2c:Vehicle>
      </nrs2:StandardResponse>
    </nrs2:RegistrationStatus>
    <n2:OriginalTextResponse>LIC/ABC###.LIY/2015.LIT/PC.
LIC:ABC###                     EXPIRE: 08/31/2017
NAM:SMITH,W,JOHN                  CUST#:D0#######
ADR:123 FAKE LN APT 20B
CTY:TEMPE                    ST:AZ ZIP:852827036
MSGS: PLATES NOT VALID FOR HIGHWAY USE
MSGS: PLATE IS FOR CREDIT ONLY PREVIOUS VEH INFO BELOW
VIN:12345678912752545 VYR:2000  VMA:TOYT    VST:4DSD</n2:OriginalTextResponse>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 2: A Parsed Vehicle Registration Match List Response.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>PRR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>CTVIN0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[NL0000TEST]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:21</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:21</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00284</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="PRR">
    <n2:OriginalTextResponse>SMITH JOHN M                         DOB/810807    SEX/M
      PO BOX 1111            STONINGTON       CT
      LIC/ABC12     LIY/1602  LIT/TM              VIN/AAAAA11A11A111111
      VYR/09  VMA/TOYOT  VMO/TACOMA D  VST/CW      VCO/GRY
      *
      SMITH JOHN M                         DOB/810807    SEX/M
      PO BOX 1111            STONINGTON       CT
      LIC/ABC1234   LIY/1808  LIT/ZZ              VIN/AAAAA11A11A111111
      VYR/09  VMA/TOYOT  VMO/TACOMA D  VST/CW      VCO/GRY
      
      </n2:OriginalTextResponse>
    <nrm2:RegistrationMatch xmlns:nrm2="http://www.nlets.org/niem/nlets-registration-match/1.0">
      <nrm2:IndividualMatch>
        <nc:ConveyanceRegistration>
          <nc:RegistrationExpirationDate>
            <n2:DateText>1602</n2:DateText>
          </nc:RegistrationExpirationDate>
          <n2c:RegistrationHolder xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
            <nc:ContactMailingAddress>
              <nc:StructuredAddress>
                <nc:LocationStreet>
                  <nc:StreetFullText>PO BOX 1111</nc:StreetFullText>
                </nc:LocationStreet>
                <nc:LocationCityName>STONINGTON</nc:LocationCityName>
                <nc:LocationStateName>CT</nc:LocationStateName>
              </nc:StructuredAddress>
            </nc:ContactMailingAddress>
            <n2c:Person>
              <nc:PersonBirthDate>
                <n2:DateText>810807</n2:DateText>
              </nc:PersonBirthDate>
              <nc:PersonName>
                <nc:PersonFullName>SMITH JOHN M</nc:PersonFullName>
              </nc:PersonName>
              <nc:PersonSexCode>M</nc:PersonSexCode>
            </n2c:Person>
          </n2c:RegistrationHolder>
          <nc:ConveyanceRegistrationPlateIdentification>
            <nc:IdentificationID>ABC12</nc:IdentificationID>
          </nc:ConveyanceRegistrationPlateIdentification>
          <nc:ConveyanceRegistrationPlateCategoryText>TM</nc:ConveyanceRegistrationPlateCategoryText>
        </nc:ConveyanceRegistration>
        <nc:Vehicle>
          <nc:ConveyanceColorPrimaryText>GRY</nc:ConveyanceColorPrimaryText>
          <nc:ItemModelYearDate>09</nc:ItemModelYearDate>
          <nc:PropertyStyleText>CW</nc:PropertyStyleText>
          <nc:VehicleMakeText>TOYOT</nc:VehicleMakeText>
          <nc:VehicleModelText>TACOMA D</nc:VehicleModelText>
          <nc:VehicleIdentification>
            <nc:IdentificationID>AAAAA11A11A111111</nc:IdentificationID>
          </nc:VehicleIdentification>
        </nc:Vehicle>
      </nrm2:IndividualMatch>
      <nrm2:IndividualMatch>
        <nc:ConveyanceRegistration>
          <nc:RegistrationExpirationDate>
            <n2:DateText>1808</n2:DateText>
          </nc:RegistrationExpirationDate>
          <n2c:RegistrationHolder xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
            <nc:ContactMailingAddress>
              <nc:StructuredAddress>
                <nc:LocationStreet>
                  <nc:StreetFullText>PO BOX 1111</nc:StreetFullText>
                </nc:LocationStreet>
                <nc:LocationCityName>STONINGTON</nc:LocationCityName>
                <nc:LocationStateName>CT</nc:LocationStateName>
              </nc:StructuredAddress>
            </nc:ContactMailingAddress>
            <n2c:Person>
              <nc:PersonBirthDate>
                <n2:DateText>810807</n2:DateText>
              </nc:PersonBirthDate>
              <nc:PersonName>
                <nc:PersonFullName>SMITH JOHN M</nc:PersonFullName>
              </nc:PersonName>
              <nc:PersonSexCode>M</nc:PersonSexCode>
            </n2c:Person>
          </n2c:RegistrationHolder>
          <nc:ConveyanceRegistrationPlateIdentification>
            <nc:IdentificationID>ABC1234</nc:IdentificationID>
          </nc:ConveyanceRegistrationPlateIdentification>
          <nc:ConveyanceRegistrationPlateCategoryText>ZZ</nc:ConveyanceRegistrationPlateCategoryText>
        </nc:ConveyanceRegistration>
        <nc:Vehicle>
          <nc:ConveyanceColorPrimaryText>GRY</nc:ConveyanceColorPrimaryText>
          <nc:ItemModelYearDate>09</nc:ItemModelYearDate>
          <nc:PropertyStyleText>CW</nc:PropertyStyleText>
          <nc:VehicleMakeText>TOYOT</nc:VehicleMakeText>
          <nc:VehicleModelText>TACOMA D</nc:VehicleModelText>
          <nc:VehicleIdentification>
            <nc:IdentificationID>AAAAA11A11A111111</nc:IdentificationID>
          </nc:VehicleIdentification>
        </nc:Vehicle>
      </nrm2:IndividualMatch>
    </nrm2:RegistrationMatch>
  </n2:NLETSResponseData>
</n2:NLETS>


Top

Legacy (DEPRECATED)

Vehicle Registration Legacy Specifications

This section provides Legacy format and examples for Vehicle Registration Query by License Plate/Year/Type, or VIN to a state (RQ), and the corresponding Vehicle Registration Response (RR), and the Vehicle Registration Query by License Plate/Year/Type, or VIN to a region (RQG). An alternative Vehicle Registration Query is by name (RNQ) with the corresponding Vehicle Registration Response (RNR).

Canadian vehicle registration queries are described in "Communicating with Canada".

Mexican vehicle registration queries are described in "Communicating with Mexico".

Formats for Vehicle Registration queries and responses are described in the sections that follow.

Query Formats

  • All inquiries and responses are in a fixed format.
  • All messages are preceded by a standard input header.
  • If a regional code is used, the message type should be RQG. If it is not, Nlets will change it to RQG and handle it at a lower priority.
  • States receiving an RQG will respond with an RR.

To send a vehicle registration query, enter the following:

RQ. or RQG.
Sending ORI followed by a period.
Destination ORI followed by a period (up to 5 2-character state codes or regional codes).
If needed, optional control field.
TXT
Carriage return, line feed, delete control character (optional).
Enter either:

-"LIC/" followed by license plate number (alphanumeric only) and a period.
-"LIY/" followed by year of current license or NX (non-expiring) and a period.
-"LIT/" followed by license type.

 OR-

-"VIN/" followed by vehicle information number (and a period if VMA or VYR is present).
-"VMA/" followed by vehicle make and a period (required only for MO).
-"VYR/" followed by vehicle year of manufacture (required only for MO).

  • No imbedded spaces and no special characters (i.e. hyphens) should be in the query.
  • All data elements (i.e. license or vehicle ID number) are preceded by a prefix and terminated by a period. The final character should not be a period (this conforms to NCIC message structure).
  • Control characters are permitted throughout the text of the message and should be ignored by the queried state when examining the inquiry.
  • Nlets provides access to the Department of State Diplomatic License file. Queries are formatted exactly the same as for a state except the 2-character code used is "US".

The format for vehicle registration query on a license number is:

Entry # Char. Explanation
RQ. or RQG. 2 Message type followed by a period.
Message Header 13-36 Standard input message header may include control field
and up to 5 addresses (state or regional codes).
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
LIC/ 4 Prefix to identify license plate.
License number 1-10 License number, alphanumeric only, followed by a period.
LIY/ 4 Prefix to identify license year.
License year 2-4 License year followed by a period; 2-4 numeric digits
designating year of current license or NX, for non-expiring.
LIT/ 4 Prefix to identify license type.
License type 2 License type; 2 character designating type of license.

The format for a vehicle registration query on vehicle identification number is:

Entry # Char. Explanation
RQ. or RQG. 2 Message type followed by a period.
Message Header 13-36 Standard input message header may include control field
and up to 5 addresses (state or regional codes).
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
VIN/ 4 Prefix to identify VIN.
Vehicle ID # 1-20 Vehicle ID # followed by a period.
VMA/ 4 Prefix to identify vehicle make.
Vehicle make 2-4 Vehicle make followed by a period (optional).
VYR/ 4 Prefix to identify vehicle year.
Vehicle year 2-4 Vehicle year of manufacture.

The format for a vehicle registration query by name is presented below. Note that the message key is different then a normal vehicle registration query.

Entry # Char. Explanation
RNQ. 3 Message type followed by a period
Message Header 13-24 Standard input message header, may include control field
but only a single 2 character state code
TXT 3 Fixed filed prefix to beginning of message
CR,LF,DEL 3 Control characters (optional)
NAM/ 4 Prefix to identify name
Name Max. 30

This field must include at least a first and last name in the
standard name format (surname, first name). Some states
allow a question mark "?" in the surname if the full
surname is not known. Consult state help files to
determine if a state can support this capability. (E.g.,
NAM/PUBL?, JOHN Q.)

DOB/ 4 Prefix to identify date of birth (optional)
Date of Birth 6 or 8 This field, if used, must include the complete date of birth.
AGE/ 4 Prefix to identify age (optional)
AGE 2

If a complete date of birth is unknown some states support
inquiries on age. Consult state vehicle registration HELP
file for details. The address is xxLICHELP where xx=2
character state code.

Response Formats

  • Should the information be unavailable, a standard message is returned by the state.
  • If the query was processed and there was no information on file, a standard "no record" message is returned. The format for each of these follows the positive response format.
  • If a data field presented in the format is unavailable, the prefix, data element, and period should be omitted from the response.
  • The message should be compacted to eliminate spaces resulting from missing or unavailable data elements. An example of this would be vehicle color. Some states do not have this information on their database.

All responses to RNQ inquiries must have a message type of "RNR" but otherwise are identical to RQ responses (RR).

The only discriminators between RQ/RR and RQG examples are as follows:

  • The destination Agency ORI in a RQG must be a regional code.
  • The message type must indicate a region message by including "G".
Vehicle Registration Legacy Examples

Example 1: A Vehicle Registration query by license plate, year and type.

RQ.AZNLETS20.CA.TXT
LIC/AAAAAA.LIY/2011.LIT/PC

Example 2: A Vehicle Registration query by VIN.

RQ.AZNLETS20.CA.TXT
VIN/AAAAA11A11A111111

Example 3: A Vehicle Registration response.

RR.CALIC0000
09:12 10/06/2011 04364
09:12 10/06/2011 00438 AZNLETS20
TXT
DATE: 10/06/11 TIME: 09:12
IDENT: OFF HIGHWAY VEHICLE

LIC #: AAAAAA LAD:09/09/09
DATA REMOVED FROM AMIS - VEHICLE SUBPLATED TO XXXXXX
MORE

DATE: 10/06/11 TIME: 09:12
IDENT: OFF HIGHWAY VEHICLE
PNO VALID FROM: 06/14/10
REG VALID FROM: 06/30/08 TO 06/30/10
LIC#: XXXXXX YRMD:02 MAKE:YAMA BTM :TR VIN :AAAAA11A11A111111
R/O :JOHN SMITHPO BOX 1111 CITY:SAN BRUNO C.C.:30
ZIP#:99999
SOLD:00/00/02 RCID:11/06/08 OCID:02/10/02 LOCD:9 ENG#:A111A111111
PNO-REGISTRATION DEFERRED
11/06/08 PREV LIC AAAAAA

END

Example 4: A Vehicle Registration query by Region. The response will be a standard Vehicle Registration response (RR).

RQG.AZNLETS20.A1,B1,C1.TXT
VIN/AAAAA11A11A111111

Example 5: A Vehicle Registration query by name.

RNQ.AZNLETS20.AZ.TXT
NAM/SMITH, JOHN.DOB/19500101

Example 6: A Vehicle Registration response by name.

RNR.AZLIC0000
13:51 10/26/2011 45282
13:51 10/26/2011 01948 AZNLETS20
TXT
NAM/SMITH,JOHN
RESPONSE FROM ARIZONA DMV REGISTRATION RECORDS PAGE 001
SMITH, JOHN 1234 ANY STREET PHOENIX AZ
LIC/1234567 LIY/2010 LIT/PC VYR/2005 VMA/STRN VMO/ION VST/4D VCO/WHI
END OF SEARCH

Top

Downloads

Download PRR Schema

Download PRR Stylesheet (updated 2/19/2020)

Download RQ Schema

Download RQ Stylesheet

Download RR Schema

Download RR Stylesheet (updated 02/18/2020)

Download RQG Schema

Download RQG Stylesheet

Download RNQ Schema

Download RNQ Stylesheet

Download RNR Schema (Updated 02/20/2020)

Download RNR Stylesheet

CANDLE Specifications

Top