Express Entry:FAQ

From Melissa Data Wiki
Jump to: navigation, search

← Express Entry

In the Fielded Input example or the sales demo page, my address A is in city B. Why does A appear also in city C?

Due to the presence of non-official cities (vanity names), Fielded Input is set up not to pass the city name. This means that your address, after selecting the ZIP code, may appear to be in both cities B and C if you test the data. Fielded Input is set up to search the ZIP Code, not the city, for a given address.

Why is the city returned different than expected?

In Free Form Entry, only the official U.S. Postal Service deliverable city names show up in a given ZIP code. This means that when entering an address, you may be given a city different than your expected city. Because of the way standardization is for addresses within the United States Postal Service and the data, the address that Express Entry returns is actually the official deliverable city for that ZIP code. Deliverability is not affected by the city being different than expected in this case.

What are the requirements for Express Entry?

Express Entry consists of a web service which is accessed by your client. The client code can be any language that supports REST or JSONP queries and XML or JSON responses.

Sample code is available in C#.NET, Visual BASIC.NET, and JavaScript/JQuery.

How does Express Entry work?

The client code forms a secure query in REST (the Web standard.) For example:[LicenseKey]&maxrecords=10&format=XML&line1=9000+R

This consumes (receives) the completed information via XML or JSON. Using the Visual Studio libraries, parsing XML is simple – just search for the desired node using a string and traverse the siblings (see samples).

How many keystrokes can I expect to save?

With Express Entry, you can expect to cut your keystrokes in half.

I found an address that is not in the system. What should I do?

Your code will need to support the entry of the full address if it is not found in the database.

Personal tools