Quickstart Guide

Express Entry Advisory

Introduction

*Express Entry Major Update:(v4 Release)

Beginning July 5, 2021, our Express Entry API will be updated from Version 3 to version 4, introducing back-end architectural improvements on the address completion engine in order to give better results. We expect all changes to the service to be backwards compatible. However, this may not be the case for some integrations, especially those using older technologies that would otherwise be incompatible with the new the new version’s header structure. This is also true for users who have stricter implementations that are not able to dynamically handle changes to the API response headers. Express Entry Version 4 also introduces several changes and improvements to how the search algorithm works, causing the data returned in the response to change. We are strongly advising all our subscribers to test the beta endpoint in order to ensure the compatibility of your integration moving forward and that all business requirements are still met.

Why are we updating to Version 4?

In order to stay relevant in the Industry, Melissa continuously improves and evolves it’s APIs. As we move to the future, we are making several back-end improvement in order to accommodate the ever changing needs of our clients. This primarily includes:

  1. Conversion to container technology to increase stability and reduce maintenance/update times
  2. Conversion to .NET Core
  3. Improved search engine, overall providing better results for auto completion
  4. Optimizations to increase overall processing times

For all inquiries, issues and questions please contact Melissa Tech Support.

What is the Update Timeline?

JULY 5, 2021

We will be updating Express Entry from Version 3 to Version 4 on the week of July 5th, 2021. Please make sure to test the beta endpoint of Express Entry to ensure that your application/integration is compatible with the new version.

What will happen if I cannot connect to Express Entry v4 by the deadline?

If your integration is not backwards compatible with Express Entry v4, your application may stop working or crash.

How Can I Test if My Application Will Work with Express Entry v4??

In order to test your application for compatibility with Express Entry v4, you will need to point your application to the v4 Beta URL. Please make the following changes to the URL in the application or in your code:

Production v3:

Beta v4:

What are the Changes in Express Entry v4?

  1. Header Changes

  2. Protocols Affected Current Production (v3) Express Entry v4
    All Cache-Control: private Cache-Control: no-cache,no-store,must-revalidate,private
    All Does not Exist X-Frame-Options: deny
    X-XSS-Protection: 1
    All Does not Exist Pragma: no-cache
    All X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Does not exist
    All Server: Microsoft-IIS/8.5 Server: Kestrel
    JSONP Content-Type: application/x-javascript Content-Type: application/json; charset=utf-8
  3. Search Algorithm Changes

  4. With the conversion of the Express Entry code to .NET Core, the engine for auto complete searches was also re-worked in several areas. These changes ultimately provide more optimal processing time overall and reduce the number of unnecessary results when searches are too vague. What this means is that the information returned between v3 and v4 will likely be different when there are more than 10 records returned (which usually occurs with 6 keystrokes or less). This change however, is not an indication of an error as internally, the order of the records returned may be different between v3 and v4 whenever there are too many results.

    Also with the re-work of the engine, the service may also return different responses when there are typographical errors in the input. Overall, v4 improves the way it is able to handle incorrectly typed/entered values. However, there will be cases where v4 is able to find results for certain searches with misspellings, while v3 does not, and vice versa.