---
title: "Create member"
method: POST
path: "/members"
tags: ["members"]
---

# Create member

`POST /members`

This endpoint allows you to create a new member. Standard members are created with the required parameters credentials and `institution_guid`. 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. <br></br><br></br>   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 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. OAuth members will be created with a connection status of `PENDING`; a one-time use redirect URI will be provided in the `oauth_window_uri` field of the response. Making a separate request to the `oauth_window_uri` will then take the end user to the registered OAuth application where they can provide credentials and choose what data to share with MX. <br></br><br></br>   After completing the OAuth process, aggregation will automatically begin and the connection status will be updated, unless the `skip_aggregation` parameter was set to true. Partners should not add multiple members to a user if they are connecting to the same institution using the same credentials. This is not supported by many data providers and will result in undefined behavior. This restriction also applies to OAuth members. In addition, it is important to note that the name field is rarely necessary in a member create request. The preferred option is to omit the field and use the default name, i.e. the name of the institution set up by an MX Integration Engineer. <br></br> <br></br>  Only in rare circumstances would the name field be supplied in a member create request, and it should not be used unless you have discussed it with a MX Integration Engineer. This endpoint accepts the optional `MX-Skip-Webhook` header and `skip_webhook` parameter.

## Response `200`

OK

---

[API](https://skmtc.net/mx/apis/consent-management-v4-api.md) · [All operations](https://skmtc.net/mx/apis/consent-management-v4-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mx/consent-management-v4-api/revisions/bf6bb86ee0c8/schema)