# Retrieve all Recurring Donation Setups
source: https://developer.mastercard.com/donations/documentation/use-cases/manage-recur-donations/retrieve-all-recur-donations/index.md

## Overview {#overview}

The **Get All Recurring Donation** endpoint retrieves all recurring donation setups for the donor ID provided in the request.

To retrieve the setups of all recurring donations available for a donor profile, you need to supply:

* **Donor identifier** : The unique `donorId` that the Mastercard Donate service created at the time the donor enrolled.
* **Limit**: The number of donation setups to retrieve.
* **Offset** : The offset which is the page number from where the donation setups are to be extracted.   

  For example, if the limit is 25 and the offset is 0, then the endpoint retrieves all records starting from the first setup up to the 25th setup, but if the limit is 25 and the offset is 1, then the endpoint retrieves all records starting from the 26th setup up to the 50th setup.

## Sequence Diagram {#sequence-diagram}

The following outlines the sequence of events:
Diagram retrieve-all-recur-donations

## Execution Steps {#execution-steps}

The following details the steps in the above sequence diagram:

1. The donor requests to view the details of all the recurring donation setups configured for its profile.
2. The partner user interface forwards the request to the partner server.
3. The partner server previously called the deprecated `GET /donors/{donor_id}/setups` endpoint with the `donor_id`, `limit`, and `offset` parameters. Partners should now use the `GET /donors/{donor_id}/donation-setups` endpoint with the same parameters when calling the Mastercard Donate Service.
4. The Mastercard Donate service validates the request and verifies if the donor ID is valid.
5. The Mastercard Donate service returns all the recurring donation setups matching the donor ID if it finds the donor ID. It also filters the response as per the values provided in the limit and offset.
6. The partner server sends the donation setup details to the partner user interface.
7. The partner user interface displays donation setup details on the end-user screen.
8. The Mastercard Donate service sends the error message 'Provided donor ID is not valid. Please check and provide a valid unique ID' to the partner server if it does not find the donor ID.
9. The partner server forwards the error message 'Provided donor ID is not valid. Please check and provide a valid unique ID' to the partner user interface.
10. The partner user interface displays the error message 'Provided donor ID is not valid. Please check and provide a valid unique ID' on the end-user screen.

## Endpoint {#endpoint}


API Reference: `GET /donors/{donor_id}/setups`


API Reference: `GET /donors/{donor_id}/donation-setups`

## Endpoint Parameters {#endpoint-parameters}

For more details on the endpoint parameters, refer to the [Parameters to Retrieve all Recurring Donation Setups](https://developer.mastercard.com/donations/documentation/parameters/manage-recur-donation-param/retrieve-all-donation-setups/index.md) section.

## Sample Request and Response {#sample-request-and-response}

For more details, refer to the [Retrieve all Recurring Donation Setups](https://developer.mastercard.com/donations/tutorial/donation-api-details/monthlyapi/index.md#get-donations) tutorial.