You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
latompa
changed the title
using same generated api client in multiple environments
using the generated api client in multiple environments
Jul 22, 2022
Hey, Thomas. I researched a bit and thought you could create a wrapper around it to include config management, specifying the base url and define a config object that holds the base url for each environment
Heya, I generated a C# client from the openapi spec.
I noticed the generated API client will call paths relative to sandbox
For example TokenizeApi.CreateTokenizeWithHttpInfoAsync
Notice the path
...PostAsync<TokenizeResponseSchema>("/digitization/static/1/0/tokenize",
This works in sandbox,
baseURL
https://sandbox.api.mastercard.com/mdes
+ path/digitization/static/1/0/tokenize
However if I were to use the same client in mtf or prod, the resulting path would include
/digitization/static/1/0
, which would fail.According to the api reference, the environment domains are:
I could hack TokenizeApi (and the other Api classes) to
...PostAsync<TokenizeResponseSchema>("/1/0/tokenize",
and use different baseURLs like
Works, but it's a hack. What am I missing here?
The text was updated successfully, but these errors were encountered: