#tiggon_error
1 messages · Page 1 of 1 (latest)
👋 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/1442517706304651374
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi @dark matrix , thanks for reaching out to me. This is crypto_onramp_session id.
cos_1SX0QBRq4JxXSwrH1DpNtTlk
Do you need full payload of that request?
Do you see a request ID in the response headers?
I can't find request ID on request payload
Ah okay thanks. Can you go to the headers tab there and look in the response headers
There should be something like a X-Request-ID or something (can't remember the key)
And the value should be a request ID like req_xxxx
req_uqtaYBYkyv6gqn
Thanks let me take a look at that
Thank you
This is happeing for every on ramp session you create?
Yes, from last Friday or Saturday
Still looking, not seeing root cause yet. Give me a few more mins
Okay, I'll wait for your response
Alright @uneven thistle as far as I can tell this does not seem to be an API issue but potentially something involving an internal account configuration issue. I'm going to send you a link so you can create a Support ticket and then I can get you routed to the right spot internally to get this cleared up. But this is not the type of thing I can help with here.
Hello @uneven thistle, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442527407549714473
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
Can you let me know when you submit the Support Case via that DM?
Okay, I'll ping you after DM
But actually, I already created a ticket on that Support page.
If you already have an open ticket then you are best off working with our Support team. Providing them the request ID you shared with me above would help them expedite getting your account looked into.
I created 23 hours ago. Was it created successfully? I've got this email.
If you got that email then yes.
If you want to submit via the DM then I may be able to help route a bit quicker as well.
Up to you
A DM got sent to you
Follow the information in that DM to submit a ticket
Then let me know when you have done so.
After that our Support team will follow up over email. That's the best thing I can do for you since this isn't an API issue.
Okay, thank you for your guide
@uneven thistle did you submit the ticket via the DM?
No, I'm just asking about status of my ticket I've created yesterday