Skip to main content

Workflow Diagram

A workflow diagram of the OAuth in browsers
1

Create a Member

To create an OAuth member, set "is_oauth": true.We recommend always including a unique id when creating any Platform API resource to simplify syncing between your systems and ours.To choose which products aggregate after a successful OAuth connection, include the data_request.products parameter in your request.Endpoint: POST /users/{user_guid}/members
Do not set "referral_source": "APP" in the oauth object in browser implementations — it breaks OAuth flows. In typical browser environments, omit this option or set it to "BROWSER" explicitly.
2

Load the OAuth URI

Load the oauth.authorization_url from the last step for the end user.Authorization URLs are one-time use. Don’t hard code an expected URI into your application. To get a new URL, use the create OAuth authorization URL endpoint (POST /users/{user_guid}/members/{member_guid}/oauth/authorization_url).Don’t prepend https:// to the URI string; MX includes it.Here, the user interacts with the institution’s OAuth page and chooses what data to share with MX and, therefore, with you.
3

MX's OAuth Complete Page Loads

The user is redirected to an MX webpage that shows the final state of the OAuth process and delivers success or failure postMessages.You must capture these postMessages, which are one of the following:

OAuth Complete Error PostMessage

Triggers when the OAuth process ends in an error state. The OAuth UI sends the oauthComplete/error message, which is used in API implementations.Error Reasons
JSON

OAuth Complete Success PostMessage

Triggers when the OAuth process completes successfully.
JSON

The process is complete

The OAuth process has ended in success or error. You can close the OAuth window and redirect the user as your use case requires.