1. Create a Member
Now we’ll need to create an OAuth member, which you can do by setting the following:"is_oauth": true.client_redirect_urlin theoauthobject so we can send you UI messages with the right scheme. This can be any string, but we’ll usehttps://mx.comin this guide."referral_source": "APP"in theoauthobject tells MX to use theclient_redirect_urlyou provided so you can get back to your app.
id when creating any resource on the Platform API so you can easily sync between your systems and ours.
Endpoint: POST /users/{user_guid}/members
2. Load the OAuth URI
Now that you’ve got theoauth.authorization_url from the last step, load it in an ASWebAuthenticationSession (iOS) or Auth Tab (Android).
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 the https:// protocol to the URI string, as MX includes this.
This is where the user will interact with the institution’s OAuth page and determine what data will be shared with MX and, therefore, with you. Once the end user is done, they will be redirected to the URL you provided for oauth.client_redirect_url. We’ll append information to this URL about success/error as well as the member GUID.
Example client_redirect_url with Appended Information

