Select, Get Counts, and Purchase Targeted Occupant Mailing Lists
Do any of the above in real-time, anytime
Basic Order of Operations
Set up the request: license key, options, ect.
Send the count request: This call returns an XML document showing the record counts for a specific request, allowing you to see how many records are available for the selected parameters.
Send the buy request: This call initiates the purchase of the list detailed by the request. This call is similar to the Get call, but has additional information returned. This information is the order ID, number of usage, and download URL. If the purchase of the list was successful, you will receive a link to the list file in the format you selected in the options.
Download/ retrieve list: download the list from HTTPS link in the buy call response.
Simply replace [your Melissa license key] with your license key to test these requests. It will also work in any browser.
REST - Count
Use a REST request to get the count.
curl -X GET "http://list.melissadata.net/V1/occupant/rest/Service.svc/get/zip?id=[your Melissa license key]&zip=90602,92688&crrt=c061-90602,c062-90602,b007-92688&name=1"
REST - Purchase
Use the REST request to purchase the list.
curl -X GET "http://list.melissadata.net/V1/occupant/rest/Service.svc/buy/zip?id=[your Melissa license key]&zip=90602,92688&crrt=c061-90602,c062-90602,b007-92688&name=1&file=8"
HTTPS - Download
Use the HTTPS link to download the purchased list.
Required: zip Optional: radius by miles, radius by records, city, county
Each five-digit ZIP is validated For radius by miles and radius by records types, either ZIP or the city and state combination needs to be entered. For city and county types, request can be narrowed down by specifying ZIP(s) within the city/county.
Optional: zip, city, radius by miles
Format validation: carrierRoute-ZIP (dash between carrier route and zip) The ZIP part must be consistent with the zip parameter above. Carrier route is used as filter in selection. If no occupant is within the requested carrier route(s), nothing will be returned. Multiple carrierRoute-ZIP’s can be entered as comma separated with no space. For radius by miles type, request can be narrowed down by specifying carrier route(s) within the mileage of the given address.
Required: city Optional: radius by miles, radius by records
Each city and state combination is validated. For radius by miles and radius by records types, either ZIP or the city and state combination needs to be entered.
Each county and state combination is validated. FIPS is retrieved if valid.
Required: county, city Optional: radius
Two-digit state code is validated in combination with city or county depends on the geo type. For radius by miles and radius by records types, either ZIP or the city and state combination needs to be entered.
Required: radius by miles, radius by records
Exact street number and street name are used in data selection No validation. Latitude and longitude are retrieved if the address exists.
Required: radius by miles
Mile is used to find out the latitude and longitude of a parameter so many miles away from the given address.
Required: radius by records
Number of records that are the closest to the given address (within 10 mile radius).
Occupant Request Parameters
To include city deliveries – residential addresses
Default: cityres =1 To exclude: cityres=0
To include city deliveries – apartments
Default: cityapt =1 To exclude: cityapt =0
To include city deliveries – business addresses
Default: citybiz=1 To exclude: citybiz =0
To include PO boxes - residential addresses
Default: pores =1 To exclude: pores=0
To include PO boxes – business addresses
Default: pobiz =1 To exclude: pobiz=0
To include rural routes – residential addresses
Default: ruralres=1 To exclude: ruralres=0
To include rural routes - apartments
Default: ruralapt =1 To exclude: ruralapt=0
To include rural routes – business addresses
Default: ruralbiz=1 To exclude: ruralbiz=0
Input Best Practices
While text encoding is a rare issue with LeadGen Occupant Web Service, note that the API will not support any wrongly-encoded special characters or non-Latin characters. In general, text encoding is an important part of any data enterprise.
This service can deal with multiple languages and scripts. It expects UTF-8 encoding. Be on the lookout for question marks (?), squares (▖) or other unwanted characters like �. They may be an indication of encoding issues and may result in data loss. Bad encoding or character loss is not something our service can correct for you.