Support for dynamic baseURL or liveEndpointUrlPrefix configuration in API clients

[Jijithnair]

Hi Team,

Currently, the PaymentsApi and similar classes in the Adyen Java API client module (checkout) require the baseURL or liveEndpointUrlPrefix to be defined at construction time. Once the API instance is created, there appears to be no supported way to override or change this value dynamically at runtime.

This becomes limiting in scenarios where different request contexts may require different endpoint routing, such as switching between regional prefixes or environments.

I would like to know the design reasoning such that introducing 'dynamic' behaviour here can go wrong. That brings me to my next query on the possibility to consider an enhancement that allows setting or overriding the base URL dynamically per request — or at least decouple it from being hardcoded in the constructor? Even exposing a method to set the liveEndpointUrlPrefix or baseURL after construction would help in advanced routing scenarios.

Thanks for your consideration!

Code reference:

adyen-java-api-library/src/main/java/com/adyen/service/checkout/PaymentsApi.java

Line 39 in ce9367f

protected String baseURL;

[gcatanese]

Thank you for reporting this, it is a valid question. Here are the considerations and reasons of our design:

• runtime switch between test and live: we don't support this, to avoid mistakes that would send live keys to test.
• runtime update of liveEndpointUrlPrefix should not be necessary as each company has one prefix only
• runtime update of Terminal API regions is not recommended and will be soon not supported

If you elaborate further your use case, with some examples, we are happy to discuss if there is an opportunity to update and improve the integration experience.

[Jijithnair]

runtime update of liveEndpointUrlPrefix should not be necessary as each company has one prefix only

@gcatanese This is not necessarily the case always right, as at least in our case, we have a multi tenant setup, and we intend to keep different company accounts for that. This can also vary according to the market for ex. EMEA for compliance and other operational reasons. In such cases, passing a url to the client at the runtime based on the tenant/ market is something we would like to have rather than creating a client bean upon each request/ caching the beans which introduces unnecessary complexity.

[github-actions]

This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs.

[Jijithnair]

@gcatanese Please let me know your thoughts!