Language to use: C#

I have a situation where I have around 4/5 api calls to make but they are all dependent on the previous API call being successful.

For example:

1. CommandA
2. CommandB(Uses Result of CommandA)
3. CommandC(Uses Result of CommandB)

and so on and so forth - it really as simple as that. I have bneen recommended the builder pattern, Chain of responsibility and command pattern but don't know which one would be the easiest to build upon if i have to add any more commands later on down the line. Thanks.

For more context, I am trying to create a spotify playlist generator that takes in multiple different sources. 

I currently have it set up so it has 2 flows - random songs and setlist fm songs.

the flow of the random songs is

* Check if playlist exists(create if not) (CommandA)
* Remove songs in playlist if specified(CommandB)
* Get Random Songs (CommandC)
* Add songs (CommandD)

and the flow for setlist fm is
 - CommandA
 - CommandB
 - Scrap setlist fm for songs
 - CommandD

here is an example code snippet:

```
    public ResponseCode GeneratePlaylistWithSongs(string playlistID, List<string> trackList)
    {
        PlaylistValidationResponseMessage playlistValidationRM = ValidatePlaylist(playlistID) as PlaylistValidationResponseMessage;
        if(playlistValidationRM.ResponseCode == ResponseCode.SUCCESS)
        {
            SongGetResponseMessage songGetResponseMessage = GetSongTracks(trackList) as SongGetResponseMessage;
            if(songGetResponseMessage.ResponseCode == ResponseCode.SUCCESS)
            {
                GeneratePlaylistResponseMessage generatePlaylistRM =
                    GeneratePlaylist(playlistID,
                    SourceType.SETLISTFM,
                    songGetResponseMessage.Track)
                    as GeneratePlaylistResponseMessage;

                return generatePlaylistRM.ResponseCode;
            }
        }
        return ResponseCode.FAILURE;
    }

```

as you can see, if i wanted to add any more to this flow i would just create a lot of if-elses on the response messages.