Our authentication credentials (license and guid) ca now be optionally sent using HTTP basic auth instead of sending them in the request body. If you want to use HTTP basic auth for our API authentication simply send the license key as user and the guid as password.
We have implemented a new API route to fetch social media information such as number of followers by an email address. Available social media profiles are LinkedIn, XING, Facebook, Twitter, Instagram, Youtube, Google and Klout.view API documentation
We have implemented a new API route to calculate the phonetic code for any given text. Currently the following algorithms are supported: Soundex, Colcogne Phonetic and Metaphon.view API documentation
The response key download_content_length is now marked as deprecated and will be removed in version 2.0.0.view API documentation
The formatted phone number will now be returned as response even if we could not verify its existence. This may occur if the mobile number has a valid spelling but we can not communicate with its carrier right now.view API documentation
We have added a bunch of new first names to our collection and updated the gender of a few first names. There are currently ~42,000 entries in our collection.view API documentation
We have extended the list of countries for which companies can be found. The following countries were added: France, Ireland, Netherlands, Norway and Romania.view API documentation
We have fixed a bug for greylisted and mail server currently unavailable results as there were marked as invalid instead of an unknown state.view API documentation
We have fixed a bug where the remaining part of the given text / full name were manipulated if it contains any first name found like 'Ivan Ivanov'.view API documentation
We have fixed a bug where the function returned the correct state name but matched to an invalid state code. This case occurred for Italian addresses only.view API documentation
In order to accept multiple languages and character sets for all request data we have unified our character encoding to UTF-8. This means all request data will be checked for UTF-8 encoding. Please keep in mind to always encode your data to UTF-8 before sending them to our service.
We have updated the minimum and maximum character length for request data of multiple functions.
We have implemented a new API route to find the D-U-N-S number and additional information (geo-location, phone number, branch) of a company or an organization by its name.view API documentation
We have implemented a new API route to resolve company information (official name, postal address, annual turnover, number of employees, ...) based on the company's D-U-N-S number.view API documentation
We have implemented a new API route to get marketing information about a company (credit rating, PAYDEX score, demographic information, ...) based on its D-U-N-S number.view API documentation
We have added a new third party service provider to increase the availability of our service.view API documentation
We have improved the communication with other mail servers when checking the mailbox for existence. If no MX record was found for the specified domain our logic will now check for A records which may resolve in a MX record.view API documentation
We have added a new response key to all of our email validation functions named status_code which is a unique code representing the state of the email address validated.view API documentation
We have added a new logic to improve the handling of house numbers for specific countries when using the structured query. Once again we have improved the quality of our address lookup by adding a new address provider.view API documentation
We have implemented a new API route to check if /data.mill for applications is alive or if the service is currently unavailable. If alive the route always returns http status code: 200 OK.check if /data.mill for applications is alive
We have added a new response key to return the well formatted IBAN if the specified IBAN is valid.view API documentation
We have added a new response key to return the well formatted BIC if the specified BIC is valid.view API documentation
We have added two new optional request parameters to filter the search results by country and optionally set a minimum score value to avoid inaccurate results.view API documentation
We have implemented a new API route to check if a contact is either moved or deceased. Thus you can find all contacts in your address lists which have an undeliverable state for sending letters. Currently this request works for people residing in Germany only.view API documentation
We have improved our logic to return the entire postal code for locations in UK if possible.view API documentation
Now the content type of the response is always application/json. We have added a more detailed description to all error responses which should be more comfortable for debugging and error analysis of our clients. In addition we extended our list of country codes (ISO 3166-1 alpha-2) which is used for some API endpoints.
We have implemented a batch mode for all our API endpoints to allow the transformation of multiple records combined in one request. Currently the maximum amount of records for a single request is set to 5,000 whatever API endpoint you use. To get more information about how the batch mode works simply open the documentation of your preferred API endpoint.
We have improved the error handling for all functions which uses a third party provider. If an external service is currently not available or throws any other error we will catch this error and provide a well formatted error message to our clients. In this case of course we won't charge any credits for the execution.
We have improved our business logic for cases where multiple dots are set in the house number part and for cases where the street contains no digits and the house number is empty.view API documentation
We have improved our function to check the spelling of an email address to allow addresses which contains sub-addresses or detailed address information (e.g. firstname.lastname@example.org).view API documentation
We have added a bunch of new first names to our collection and updated the gender of a few first names. There are currently ~33,000 entries in our collection.view API documentation
We have introduced a new optional parameter named direct_dialing_delimiter to define a special character (e.g. -) as delimiter between the phone number and the extension.view API documentation
We have fixed a bug for the modes exact and html where the result contained one line break too much.view API documentation
Improved error handling to avoid internal errors depending on the result of third party applications.
We have implemented a new response key named matchlevel to all routes working with postal addresses which provides detailed information about the match quality of the result. The response key contains a string describing the most detailed address component found.
- housenumber: The most detailed match level indicating that the whole address including the house number was found.
- street: The most detailed address component that was found is the street name. The house number could not be found/verified.
- general: Some of the address components were found excluding the street and house number.
In addition to the new response key we have extended our unit tests to ensure a high code coverage.
We have implemented a new API route to extract the street name, house number and additional house number parts from an unqualified single-line postal address string. Currently this function is developed for postal addresses within Europe, North and South America.view API documentation
We have added some request parameter to optional enter structured (qualified) address information instead of the unstructured single-line address query. Both types of request parameter can be mixed up in a single request. You may define some address components using the according request parameter and all other information in the pre-existing address query. Additionally we fixed a bug for returned house numbers in combination with the district.view API documentation
We have changed the verification of the requested VAT number to be case insensitive.view API documentation
In order to avoid the abuse of port scanning we have changed the functionality to only allow web resources using the HTTP protocol and default ports. A requested web resource has to start with either the http:// or https:// prefix, must not contain a specific port at the end (e.g. :8080) and must not contain any username or password information (e.g. username:email@example.com). In addition IP addresses (IPv4 and IPv6) are not permitted too.view API documentation
We have implemented a new function to check your records for duplicate entries. The search engine considers the first and last name of a person and the postal address. It uses a phonetic lookup to ignore typo errors in first and last names and a 1:1 match for the city and street. Currently this function is not available in the API documentation yet, but will be added soon. We will add more information as soon as the documentation is published.
We have implemented a new function to wrap a given text after a custom number of characters. The function allows multiple modes when the text will be wrapped (e.g. before or after a word) and different line breaks to support multiple operating systems.view API documentation
We have added the opportunity to customize the format of phone numbers returned by the API route. The custom response format is defined by an enumeration of placeholders for the different phone number parts. The phone number will be built according to the order of the placeholders set in the custom format.view API documentation
We have extended our mailbox check to improve the response for indeterminate communications with the mail server. The status of the mail server will be returned in more detail if the server has an active greylist function to prevent users from spam or if the mail server accepts mails for all mailboxes (catch all). In both cases the requested mailbox can not be verified and therefore the response will be unknown.view API documentation
We have fixed a bug to recognize first names containing special characters (e.g. René) now. In addition we have added a bunch of new foreign first names to our collection. There are currently ~34,600 entries in our collection.view API documentation
We have implemented three new response keys to all routes working with postal addresses. The state_code returns the ISO 3166-2 state code if found, the state_name returns the fully qualified name of the state and the district returns the lowest subdivision of the postal address.
We have implemented a new API route to request structured, qualified postal components. If the house number is set in the request, it will be kept unchanged. Otherwise the house number will be checked as usual.view API documentation
We have added a new response key named raw_address which returns the raw postal address received from the European financial service. To confirm other postal address API functions we have implemented a new response key named additional_data which contains all postal address parts that could not be resolved by the included address lookup.view API documentation
We have fixed a bug where sometimes an internal error was thrown if multiple first names were requested or if the first name contained special characters.view API documentation
Improved error messages if a third party application is currently not available.
We have changed a major part of these API routes. House numbers are returned only if they can be verified without any data remaining. We have implemented a new third party application to improve the quality and global coverage. In addition we have fixed a bug when the requested postal address contained special characters.view API documentation
We have improved the function to return the gender of the first part of the first name found if multiple first names are requested. Additionally we have added a bunch of new first names to our collection. There are currently ~31,900 entries in our collection.view API documentation
We have fixed a bug for requested phone numbers including the leading region code without the plus sign (+) as prefix.view API documentation
We have started to write a public changelog about all changes done in the core and in all API routes.
We have implemented a new API route to translate postal address components to a specific language according to RFC 4647 standard.view API documentation
We have updated the API route to support legal forms for companies and organisations such as Ltd. or AG.view API documentation
We have implemented a third party database to check the requested mail server against common disposable providers.view API documentation
We have updated the API function to always use the most suitable MX-record for mail server communications. Additionally the function supports greylisted mail servers now.view API documentation
We have added a new response key named phonenumber which contains the well formatted phone number if valid.view API documentation
We have added two new response keys named latitude and longitude which contains the geo-location of verified companies if the postal address information could be resolved.view API documentation
We have fixed a bug to preserve additional address information such as door, floor or apartment.view API documentation
We have fixed a bug when requesting first names containing accented characters. Therefore we extended our unit tests to avoid similar bugs in the future. Additionally we have fixed a bug when a first name contained only a single character plus the dot character. These first names are recognized correctly now and returned including the dot.view API documentation