What is a suitable design/architecture pattern for a multi-tenant microservice?

I am redesigning an existing microservice which are a few APIs, which makes several calls to other services, and share some common features like pagination/filtering/boosting/burying.

The request/response structure is different for separate APis.

For eg, APi 1 makes calls to:

Service A
Service B
Service C
Feature A
Feature B

APi 2:

Service A
Service D
Feature B
Feature C

Also, the urls for the downstream services, and some feature logic, is different for different markets.

Is there any recommended Design/Architecture pattern for such problems?