Extend history

Some institutions allow developers to access an extended transaction history with up to 24 months of data associated with a particular member. The process for fetching and then reading this extended transaction history is much like standard aggregation, and it may trigger multi-factor authentication.

POST

/users/{user_identifier}/members/{member_identifier}/extend_history

Path Parameters

Field	Required	Type
member_identifier Use either the member id you defined or the MX-defined member guid. See MX-Defined GUIDs vs IDs Defined by You.	Required	String
user_identifier Use either the user id you defined or the MX-defined user guid. See MX-Defined GUIDs vs IDs Defined by You​.	Required	String

Header Parameters

Field	Required	Type
Accept-Version MX Platform API version.	Required	String

Loading...