So my approach would be as follows:
You'd want to define an Interface that an API will implement, and then create concrete instances of that interface for each of the two types of APIs you will hit (So one interface, and two classes in your case). The interface could define an update method which would mean that any class which implements the interface must define that method. Therefore when you create the two API classes that each implement the API interface, they will each have to define a custom update method.
Or, if you have common functionality between the two API's (posting, getting, etc.) you could go the Abstract Class route, and leave the update method abstract in an overarching abstract API class. Then extend (instead of implement) that abstract class for each of the concrete APIs you need.
Then, depending on the user, you can use either of those API classes, and calling the update method will work on either of them.