#benjamin_radar-auth-rates-api

1 messages ยท Page 1 of 1 (latest)

fossil sparrowBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1432406705286807653

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

echo panther
#

Hello ๐Ÿ‘‹

Unfortunately we cannot assist with Radar specific questions here. Viewing information like the rate a which your Radar rules block/allow payments is something that is only available via the Dashboard and we do not offer assistance with the Stripe Dashboard here.

keen ridge
#

Why it is not available through API ?

echo panther
#

It isn't something we expose. I don't know the design decisions behind that but I do know that is the current state.

keen ridge
#

Will this change in the future ? It is not very efficient from an operational point of view to have someone connect to the dashboard to collect this information ...

echo panther
#

I do not see this being raised as a feature request, or on any team's road map for the future. But you can write in to Support to request that feature be provided.

keen ridge
#

Did you already take into account a suggestion from a customer for your roadmap ?

echo panther
#

No, that is what I meant when I said this has not been raised as a feature request. I have not had anyone ask for this feature outside of this thread.

keen ridge
#

My question was more generic, does it worth to ask for this feature request, or customer suggestion usually directly go to the bin ?

echo panther
#

It depends. It is useful to create them because, if someone else comes to us with a similar request, internally we find the record of the first request and add more examples of requests for it. The more examples of requests for this feature, the higher priority it will get when planning out future roadmaps.

#

Just because you're the first, doesn't mean you'll be the last.

keen ridge
#

ok

#

thx for your help

echo panther
#

Happy to shed what ๐Ÿ’ก I can ๐Ÿ™‚