Data Exchange Gateway (DEX) Portal

The MDH DEX Portal is the application intended for use with MDH data partners (internal or external) to manage access requests to MDH DEX resources.

How to get started?

Proceed to MDH DEX Portal. You will be asked for your email address and to provide a password. There is a “Register” link on the login page that will allow for creation of a new login. Once successful registration has occurred a verification email will be sent to the email provided. State of Minnesota employees may use their active directory credentials (email or username) to access the system.

I requested access to a resource, what happens next?

The primary flow of a data partner request access.

1. Data partner initiates "Request access" on a resource.
2. Resource owner receives email notification of access request.
3. Resource owner reviews request and updates data partners access status.
4. Data partner receives email notification regarding changes in the resource access status.
5. Data partner reviews change in application status on MDH DEX Portal.

I have been approved access to a resource, what’s next?

1. Proceed to MDH DEX Portal. Select the resource link you have been approved for. There will be additional details on the individual resource page. This page will help detail examples of how to connect (using curl) to the resource. In addition, the DEX Resources page has more detailed content for how to use curl as well as other integration engine configurations as we can add them. It also details error handling for messages that have been rejected.
2. Test your "Data access:" and upload a file using portal.
   1. Click the blue "Choose" button
   2. Select a local file.  The filename will replace "Choose"
   3. Click the blue button with your filename.
3. Interpret the "Data response:"
   1. If the "Status:" is not 200, MDH failed to receive or validate the message that was sent, and it will need to be resent (possible after corrections). More details on responses can be found at DEX Resources or on the individual resource page.
   2. The "Header:" indicates the return response HTTP headers.
   3. The "Response body:" is the message body.

Should I generate an API Key?

Once you have been approved for access to a resource and are ready to begin establishing a permanent integration with MDH DEX you should generate an API key. 

• The API key uses a sliding door policy to remain active. The API key must be used at least once every 45 days to stay active. If your integrations cannot guarantee a minimum of one integration every 45 days, it may be best to use basic authorization or manual upload via MDH DEX Portal resource page.
• Basic authorization uses your email and password to send data. The password will expire every 90 days and require you to reset the password before being allowed to interact will MDH DEX resources. MDH DEX Portal will prompt you to update your password once it has expired.