Atrium API
Create Member
Standard Members
When creating a standard member, you'll need to include the correct type of credential required by the financial institution, with values provided by the end user. You can find out which credential type is required with the read institution credentials endpoint.
Once you successfully create a standard member, MX will immediately validate the provided credentials and attempt to aggregate data for accounts and transactions. You can prevent this automatic aggregation by setting the skip_aggregation parameter to true.
OAuth Members
OAuth members can only be created with institutions that support it. OAuth members require no credentials, but do require you to set the is_oauth parameter to true.
New OAuth members will be created with a connection status of PENDING; e redirect URI will be provided in the oauth_window_uri field of the response. Making a separate request to the MX-provided oauth_window_uri will then take the end user to their financial institution's website where they can log in and select what data to share with MX. After completing the OAuth process, aggregation automatically will begin and the connection status will be updated, unless the skip_aggregation parameter was set to true.
oauth_window_uris are one-time use. Don't hard code an expected URI into your application.
Don't prepend the https:// protocol to the URI string, as MX includes this.
Do not add multiple members which connect to the same institution using the same credentials on the same user. This will result in a 409 Conflict error.
Request Body
| Field | Required | Type |
|---|---|---|
identifier | Optional | String |
institution_code | Required | String |
metadata | Optional | String |
skip_aggregation | Optional | Boolean |
is_oauth | Optional | Boolean |
referral_source | Optional | String |
client_redirect_url | Optional | String |
ui_message_webview_url_scheme | Optional | String |