#Jinx
wicked sentinel
pearl terrace
Hello, do you have an example request ID from a time that you got this error? (req_123)
And have you double checked that you are making this call as the platform account?
pearl terrace
Can you make the call again and either get the request ID from your code (https://stripe.com/docs/api/request_ids) or from your dashboard (https://dashboard.stripe.com/test/logs)
prime hill
Can't find any logs for the call I've made
But my test secret key works for everything else on curl. Retrieving & Getting data works for every other call
pearl terrace
Sounds like you may be using the key from a different account than you think you are using. Have you double checked your secret key against the one in your dashboard? https://dashboard.stripe.com/test/apikeys
Is this the same test key that you are using to create and connect these accounts?
prime hill
Yes
pearl terrace
Interesting. That should work then. Can you run your curl command with the --verbose and look for a line in the output that says something like
< original-request: req_1234567890
prime hill
I'm using POST as a json to the url. Where can I put --verbose?
pearl terrace
I've been doing commands like this
-u sk_test_1234567890: \
-d description="My First Test Customer (created for API docs at https://www.stripe.com/docs/api)" \
—verbose
Can you just tack on --verbose at the end of your current command?
prime hill
Took a second look at my code and it turns out it was inputting "Seller Account" instead of the actual connected account id Lol. Appreciate your help!