# Data Refresh
source: https://developer.mastercard.com/open-finance-us/documentation/products/manage/account-aggregation/data-refresh/index.md

Mastercard automatically updates the data from accounts added by customers during our nightly batch aggregation. As long as those accounts have an active `aggregationStatusCode` equal to 0, indicating the account is ready for aggregation, Mastercard continues updating the account details to stay current with the host financial institution. The `aggregationSuccessDate` field indicates the timestamp of the last successful aggregation of the account.

When there is a specific business case, account data may also be refreshed on demand by using the Account Refresh Service. Discuss with your Account Manager and Solution Engineer for further clarification.

The Refresh Service pulls fresh account data that can be retrieved through the Account Aggregation Service.
Note: Two sets of endpoints for refreshing accounts are provided. You must use the correct endpoints depending on whether you are Data Access Tiers or Standalone services:

* If you are using Data Access Tiers (ASD, AFD, or ATD), you must use the V2 Refresh endpoints.
* If you are using the standalone Account Limited Aggregation (ALA) and Transaction Access (TAU), you must use the V1 Refresh endpoints.

See [Data Access Tiers](https://developer.mastercard.com/open-finance-us/documentation/products/manage/data-access-tiers/index.md) for more information about the different tiers.

Client applications are not permitted to automate calls to the data refresh service. As many financial institutions only post transactions once per day, calling the data refresh service repeatedly is usually a waste of resources and could have an adverse impact on your integration.

The recommended timeout setting for this request is 180 seconds in order to receive a response. However, a terminated call prior to a response does not terminate the refresh. Evidence of a refresh request can be found in the `aggregationAttemptDate` field, and data can be retrieved through the Account Aggregation and Transaction Aggregation services.

### Refresh Endpoints for Data Access Tiers (V2) {#refresh-endpoints-for-data-access-tiers-v2}

If you are using Data Access Tiers (ASD, AFD, ATD), use the V2 endpoints in this section.

Refresh customer account data for all accounts:

API Reference: `POST /aggregation/v2/customers/{customerId}/accounts`

Refresh customer account data for all accounts associated with a given financial institution:

API Reference: `POST /aggregation/v2/customers/{customerId}/institutionLogins/{institutionLoginId}/accounts`

<br />

### Refresh Endpoints for Standalone Services (V1) {#refresh-endpoints-for-standalone-services-v1}

If you are using the standalone Account Limited Access (ALA) service and not using Data Access Tiers, use the V1 endpoints in this section.

Note these are not suitable if you are using any of the Data Access Tiers products (ASD, AFD, ATD).

Refresh customer account data for all accounts:

API Reference: `POST /aggregation/v1/customers/{customerId}/accounts`

Refresh customer account data for all accounts associated with a given institution login ID with a connection to the institution:

API Reference: `POST /aggregation/v1/customers/{customerId}/institutionLogins/{institutionLoginId}/accounts`