Is there a particular design pattern for well suited for accessing all endpoints on an API used in a micro-service architecture of a larger system?

I have a system where my primary backend service reaches out to another that will do more focused computation. The current way I've set this up is to make a singleton (example name incoming) API_NAMEHttpService that extends HttpClient and mirrors the RESTful controller structure. Does this make sense? Is there a better way to do this? A little open-ended, but hoping for serious feedback.