Skip to main content
PUT
Resume aggregation
Best practice is to use the resume endpoint to answer MFA challenges; however, MX continues to support partners who leverage the update member endpoint for this purpose. This endpoint allows you to respond to multifactor authentication by providing answers to MFA challenges. Aggregation is automatically resumed if the correct credentials are provided in the request, i.e., if the challenges are answered correctly. A member must have a connection_status of CHALLENGED in order to successfully use the resume aggregation endpoint; a 405 Method Not Allowed error will be returned otherwise. A 400 Bad Request error will be returned if the credentials provided are invalid.

Authorizations

MD-SESSION-TOKEN
string
header
required

MX Session Token

  • Request an API token using the read API token endpoint in the MX SSO API.
  • Exchange an API token for a session token.
    • A session token is obtained by sending a POST request to /sessions
    • The session token will be used in each request made for the user. It should be passed in an MD-SESSION-TOKEN HTTP header as shown below.
    • This session token is valid for 30 minutes from the time it was created. The 30 minute expiration counter is refreshed with each call.
    • If you send a request with an expired session token you'll receive an error code of 4011.

In documentation code examples, replace <API_KEY_VALUE> with the session token.

Path Parameters

member_guid
string
required

The unique identifier for the member. Defined by MX.

Body

application/vnd.mx.nexus.v1+json
challenges
object[]

Response

200 - application/vnd.mx.nexus.v1+json

OK

members
object[]