---
title: "Refresh member (alias for aggregate member)"
method: GET
path: "/members/{member_guid}/refresh"
tags: ["members"]
---

# Refresh member (alias for aggregate member)

`GET /members/{member_guid}/refresh`

This is an alias for `members/aggregate`. Use this endpoint to create a new aggregation job, which is the process that gathers updated account, transaction, and holding data for a given member. If you've set the `use_cases` field when creating the member, then the member's `use_case` must be set to `PFM`, otherwise a 403 will return. The response will include important information about the member's aggregation including the `is_being_aggregated` and `connection_status` fields. The aggregation can take some time to finish; you can use the the read member endpoint and track the status and completion of the aggregation as it progresses. <br></br>Detailed information on the aggregation process from start to finish can be found in the [guide](/nexus/aggregating-data).

## Path parameters

- `member_guid` string, required

## Query parameters

- `include_holdings` boolean
- `include_transactions` boolean

## 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)