Should be "Job Finalized" on success Listpk of the list the addresses belong to Up to 10 addresses to validate Address validation results Required. The primary key representing the customer for which to create a new list. The primary key representing the address of the customer that owns this list Name of the list Date representing the fileversion for this list Filename for the list List's primary key Listpk for the list to finalize Name of the company, building, apt. complex, shopping center, or other entity. MaxLength: 64 Primary address line. Required. MaxLength: 95. Secondary address line. MaxLength: 64. Last line in one string, either all components or none. MaxLength: 42. This is an id which can be provided by you. If foreignid is non-null, it will update the record with a matching foreignid if one exists. Otherwise, the record is considered new and will be created. If foreignid is not populated, a unique id will be generated and the record will be created. Foreignid's must be unique within a list. If you are doing an interactive call you should set this to "Interactive" to get all of the hint data back. Hint data will sometimes give lists of city names, secondary information, and other address related information when an address could not be confirmed. This makes it easier for a user to correct keying or spelling errors. This is the primary key to a list in which to place this record. You can update existing records in a list by populating listdetailpk or foreignid with listpk. Set to true if you are providing the parsed address inputs. Name of the city. MaxLength: 28. First name. MaxLength: 30. If providing name parsed (first, middle, last)... set nameinputparsedyn to true. Set to true if you are providing the last line inputs parsed. Last name. MaxLength: 30. If providing name parsed (first, middle, last)... set nameinputparsedyn to true. Middle name. MaxLength: 30. If providing name parsed (first, middle, last)... set nameinputparsedyn to true. Set to true if supplying the name parsed The addresse's name prefix. Ex. prefixtitleinput is "Dr." for "Dr. John Doe" 2 character state code. Ex. "TX". MaxLength: 2. The addressee's suffix that should appear at the end of the name. Ex. suffixtitleinput is "III" for "John Doe III" Name goes here when it is not already parsed. MaxLength: 66 4 digit ZIP+4 add on. MaxLength: 4. 5 digit ZIP code. MaxLength: 5. Required. This must be the primary key of a customer for which the calling user (your application) has access to, and this address belongs to. The primary key of the ListdetailRecord this record corresponds to. Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Userdata through Userdata8 are available for the end-user or integration developer to store custom data Phone number for the addressee Email for the addressee Set to true if the input fields should be updated in the database if the record already exists. A record exists if either its listdetailpk or both listpk and foreignid are found in the database. If this is false, the record will not be changed. The default is true if this field is not included in the request. Set to true when this record has an error. See errormsg. Details regarding an error. DPV Confirmation Indicators This record has the following fields: dpvconfirmind, dpvfootnote1, dpvfootnoe2, and dpvfootnote3 If you need to use these fields, here is a table of their possible values and suggested action. <table> <tr> <th>Indicator</th> <th>Footnotes</th> <th>Suggestion</th> </tr> <tr> <td>N</td> <td>AA</td> <td>Verify the address. Validated on the engine but could not be validated in the DPV process</td> </tr> <tr> <td>Y</td> <td>AA BB</td> <td>No action needed, validated to all components</td> </tr> <tr> <td>Y</td> <td>AA RR</td> <td>No action needed, address validated. Found in CMRA table with PMB information present.</td> </tr> <tr> <td>Y</td> <td>AA R1</td> <td>Validated. Found in CMRA table with PMB information present.</td> </tr> <tr> <td>Y</td> <td>AA F1</td> <td>No action needed.</td> </tr> <tr> <td>Y</td> <td>AA G1</td> <td>No action needed.</td> </tr> <tr> <td>Y</td> <td>AA U1</td> <td>No action needed.</td> </tr> <tr> <td>S</td> <td>AA CC</td> <td>Verify secondary information. It is present but cannot be confirmed in the DPV process</td> </tr> <tr> <td>S</td> <td>AA P3</td> <td>Verify the box number, could not be confirmed. It is present for this PO Box, RR, or HC address but cannot be confirmed in the DPV process</td> </tr> <tr> <td>S</td> <td>AA CC RR</td> <td>Verify secondary information. It is present but cannot be confirmed in the DPV process. It has been found in the CMRA table without PMB information.</td> </tr> <tr> <td>S</td> <td>AA CC R1</td> <td>Verify secondary information. It is present but cannot be confirmed in the DPV process. It has been found in the CMRA table with PMB information.</td> </tr> <tr> <td>D</td> <td>AA P1</td> <td>Verify the box number, it is not present for this PO Box, RR, or HC address but needed to confirm.</td> </tr> <tr> <td>D</td> <td>AA N1</td> <td>Verify secondary information. It is not present.</td> </tr> <tr> <td>D</td> <td>AA N1 RR</td> <td>Verify secondary information. It is not present. It has been found in the CMRA table with PMB information present.</td> </tr> <tr> <td>D</td> <td>AA N1 R1</td> <td>Verify secondary information. It is not present, it has been found in the CRMA table without PMB information and is not required for USPS.</td> </tr> <tr> <td>BLANK</td> <td>A1 M1</td> <td>Get correct address. This address cannot be found in CASS engine. It was not presented to the DPV process.</td> </tr> <tr> <td>BLANK</td> <td>A1 M3</td> <td>Get correct address. This address cannot be found in CASS engine. It was not presented to the DPV process.</td> </tr> <tr> <td>BLANK</td> <td>A1</td> <td>Get correct address. This address cannot be found in CASS engine. It was not presented to the DPV process.</td> </tr> <table> All messages resulting from validation. There may be duplicate and/or null messages. Messages in this field do not signify an error unless error is true. When error is false, this field contains informational error messages encountered during validation. Name of the city. MaxLength: 28. Primary address line. MaxLength: 95. Secondary address line. MaxLength: 64. Early warning flag. It will indicate a "Y" if we intentionally did not code the address because the address is new and has not been finalized by the USPS. Name of the company, building, apt. complex, shopping center, or other entity. MaxLength: 64. First name. MaxLength: 15. Last line in one string (city, state, and zip). MaxLength: 42. Last name. MaxLength: 15. Middle name. MaxLength: 15. 2 character state code. Ex. "TX". MaxLength: 2. Name when it is not already parsed. MaxLength: 66. 5 digit ZIP code. MaxLength: 5. 4 digit ZIP+4 addon. MaxLength: 4. Hint data. Hint data. Hint data. Hint data. Hint data. Finalizes the list after you are done calling web service operations. Validate up to 10 addresses in-place. If you want to receive hint data back, set mode to "Interactive" in the WsPostalinputRecord. customerpk, deliveryaddressline1Input, and lastline are all required for this operation. Creates a new list. Validate a single address interactively. If you want to receive hint data back, set mode to "Interactive" in the WsPostalinputRecord. customerpk, deliveryaddressline1Input, and lastline are all required for this operation. A WsPostaloutputRecord will be returned with answers and your original inputs. PostML service is used for interactive real-time address validation. You can determine if an address is 'good' or 'bad' by examining the dpvconfirmind and dpvfootnote fields. See "dpvconfirmind" in WsPostaloutputRecord complex type definition for more information. When using a WsPostalinputRecord as a parameter in validate or validateInteractive: deliveryaddressline1input, lastlineinput, and customerpk are all required fields. If you are interested in retreiving hint data to aid your user in correcting a 'bad'/incomplete address, you will need to set "mode" to "Interactive" in the WsPostalinputRecords you submit. The WsPostaloutputRecords that are returned may have one of the hint data fields populated, the information in these fields is tabular. Consider each record a row in a table to show your user. Hint data fields of WsPostaloutputRecord are zip4Records, cityStateRecords, stateRecords, stateCityRecords, and stateCityStreetRecords. Sample SOAP messages are located at the end of this document. -- To use this service you will need to send SOAP messages over HTTPS with a plain text UsernameToken. Code samples may be found at <a href="http://duoshare.com/developers.html">http://duoshare.com/developers.html</a>