#siroos-jafary_api

1 messages · Page 1 of 1 (latest)

orchid heraldBOT
#

👋 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/1443284290350616769

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

cursive siren
#

hello! working on a couple of other threads atm but i'll get back to you asap

#

ok looking at this now

#

but i'm bouncing between a few threads so responses may be delayed

#

ok, at least part of the problem is that you're trying to set the headers in a strange way. try it with this instead --header "stripe-version: 2025-11-17.clover", and then once you've done that share the new request ID with me

grave storm
#

Getting the same error with this cURL:

curl -G https://api.stripe.com/v1/customers/search \ --u "sk_test_xxx:"\ --header "stripe-version: 2025-11-17.clover"\ --data-urlencode query="metadata["appCustomerID"]:'xxx'"

cursive siren
#

can you share the request ID too? the one that starts with req_

grave storm
#

req_I9fI4kGtLBQOOO

cursive siren
#

the request data i'm seeing on that request ID doesn't line up with the request you showed me - can you share the exact curl command you're sending with just the secret key redacted?

#

i think something is going on with url encoding in your request

#

also have you tried using this with anything aside from cURL? like one of our SDKs? or have you tried using postman?

grave storm
#

req_AOMgBc6tAlvnTM

#

I can only use cURL from my organaization app so no alternatives for me.

cursive siren
#

can you try this? this worked for me (with my own secret key obviously)
curl -G https://api.stripe.com/v1/customers/search -u "sk_test_redacted:" --header "stripe-version: 2025-11-17.clover" --data-urlencode query="metadata['appCustomerID']:'320A54B3-7B6C-344B-92C0-1395F8CCCF59'"

grave storm
#

does not work for me 😐 Same error

cursive siren
#

can you share that most recent request ID again?

grave storm
#

req_3CZe27LR1YS6Pa

cursive siren
#

hmmm i think something goofy is happening with the URL encoding of your requests

#

where are you running these? is this just in terminal or something along those lines?

grave storm
#

I'm testing it from a FileMaker app using "Insert from URL" which is the tool for making HTTP calls from FileMaker.

cursive siren
#

hmm yeah, this is what i'm seeing for the actual raw request on yours:
query=%22metadata%5B%27appCustomerID%27%5D%3A%27320A54B3-7B6C-344B-92C0-1395F8CCCF59%27%22
vs mine:
query=metadata%5B%27appCustomerID%27%5D%3A%27320A54B3-7B6C-344B-92C0-1395F8CCCF59%27

#

that URL encoded %22 at the beginning and end is the only difference, so i think you need to experiment with ways of sending the data that don't result in that

grave storm
#

Okay, let me play with it for a minute