This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
The other option is tinker proxy implementation to set a custom variable
to identify success/fail and use that variable to determine success
criteria So in that case, auth proxy will not set this variable at all.
So you could avoid developer to choos...
does both the calls have the same request path ? if not, api product
allows to specify multiple paths. Once there are multiple paths,
separate transaction recording policies can be configured per path. So
leave the authorization specific path uncheck...
I think you might be running into some kind of monetization provisioning
issue unfortunately !! is your organization newly provisioned ? Please
create support ticket with org/proxy and all the details you already
mentioned here.
The steps followed seems to be right and expectations mentioned also
seems to be right. In order to further debug, can you trace the api call
and check the following in the ax execution - refer screenshot
mint.pngapi product is correctly resolved in
...
"what credit is available for a specific rate plan" - How do you plan to
configure credit for a rateplan? Assuming rateplan is going to have
setup fee and developer is expected to have minimum balance above the
configured setup fee. If this is true t...
