#perqin_api

1 messages · Page 1 of 1 (latest)

dawn nicheBOT
turbid summitBOT
#

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.

dawn nicheBOT
#

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

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

turbid summitBOT
night glen
#

👋 happy to help

#

would you mind giving more context please?

lyric tendon
#

In the previous thread I've mentioned that we received such error response:

{
    message: '"+12312312323" is not a valid phone number',
    param: 'shipping.phone',
    request_log_url: 'https://dashboard.stripe.com/test/logs/req_0stbl8ejJw1guQ?t=1713231726',
    type: 'invalid_request_error'
}
#

And here comes the response we received last Friday:

error: {
    message: '"1103027138" is not a valid phone number',
    param: 'shipping[phone]',
    request_log_url: 'https://dashboard.stripe.com/test/logs/req_zn9nEWcqqlJ1RL?t=1712852609',
    type: 'invalid_request_error'
}

Note that the param is "shipping[phone]", not like the one we received this week ( "shipping.phone").

#

We want to know what is happening for the hardware order API, and are there any actions we should take to, like migrate to new error response definition?

night glen
#

I'm not sure to be honest but it shouldn't be an issue for you though

#

wether it's shipping.phone or shipping[phone] both notations point to the same parameter

lyric tendon
#

Well, then what about the other fields?

#

For example, the shipping.address

night glen
#

are you getting shipping.address or shipping[address]

lyric tendon
#

Should we check both styles for all possible fields? LOL

night glen
#

no that shouldn't be the case at all

#

but since this is a beta feature the returned response might change before going GA

lyric tendon
#

We are getting shipping.address

#

OK I see. Then we will only handle the special case of phone in our code.

#

Thanks for help

night glen
#

I don't think that's necessary

#

I'm trying to look to see whether there was any changes recently that could explain this

lyric tendon
#

That would be great

#

We also want to avoid handling such special cases

night glen
#

I'm sorry it's taking me so long, but I'm trying to dig into this and it's a bit of a rabbit hole

lyric tendon
#

That's OK, just let me know in this thread when you figure it out

heavy scaffold
#

Hi! I'm taking over from my colleague. Please, give me a moment to catch up.

#

I see that you're using a very outdated Stripe API version - 2017-04-06. I don't know if we are able to make strong guarantees about it. Is it a new functionality you're building?
Also, could you try making the same request and set the latest API version? Is the problem persisting?

lyric tendon
#

Let me check with our backend dev. We should not use such old version

#

I can't find the clue but our backend dev says that the latest version for hardware order API was 2017-04-06 when we were integrating the API.

#

I think we should follow the latest one specified in the documentation (2024-04-10), but we are afraid the version change will break our application.

#

Would you kindly provide the changelogs from the 2017-04-06 to the latest version 2024-04-10? We only need those of the hardware order API, a.k.a. https://api.stripe.com/v1/terminal/hardware_*

heavy scaffold
#

There's definitely been a lot of changes in the last 7 years.
I recommend you to try sending this particular request separately with the new API version, via cURL for example, and seeing if this helps.

lyric tendon
#

I've checked the changelogs on your documentation site but it only covers range from 2020 to 2024.

heavy scaffold
#

Are you only using the Hardware order API?

lyric tendon
#

No, we also use the many other APIs, but with the Stripe's Java SDK.

#

The Hardware order API are not available in the SDK so we send HTTP requests separately.

#

So this versioning issue should only happen for the hardware order API, for us.

heavy scaffold
#

I see the API version is set explicitly on that request, so you can as well set any other version, incl. the latest one.

#

Please try and let me know if the problem persists.