#alex_api

1 messages · Page 1 of 1 (latest)

tiny pelicanBOT
#

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

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

left karma
#

👋
Are you making live requests from localhost ?

#

Ah the refressh_url and the return_url are http, you should provide https if you are making live request

#

otherwise you should make test request using test secret key

ripe fern
#

Yes live request from localhost > is this supposed to work or not?

#

What are the refresh_url and return_url > what link should I use, is there a Stripe link to use?

left karma
#

Yes live request from localhost > is this supposed to work or not?
When you create an Account Link using live secret key, you need to use https endpoints for refreshurl and return_url (what your backend is sending via this request req_3bHnxvPZEbFeNo)

ripe fern
#

Ok so using localhost won't work

#

If so, what are the refresh and return urls that I can use?

left karma
ripe fern
#

Without a backend, I can't do it?

left karma
#

What you mean ?

ripe fern
#

If I want to use Postman, what should I put in refresh_url and return_url

left karma
#

Regardless from your you are making your APi call

#

refressh_url and return_url are your endpoint

#

See in your request, your backend sent:

{
  account: "acct_1RaYvzRZeux6Q64i",
  refresh_url: "http://localhost:4242/onboard-user/refresh",
  return_url: "http://localhost:4242/success.html",
  type: "account_onboarding",
}

When making live request, you need to set the HTTPs version of these endpoints:

refresh_url: "http://localhost:4242/onboard-user/refresh",
return_url: "http://localhost:4242/success.html",

tiny pelicanBOT
daring hollow
#

hello! fyi i'm taking over for my colleague here, let me know if there are any further questions

ripe fern
#

Thanks

#

I would like to create a connected acocunt > what is the easiest option?

daring hollow
#

it sounds like you're using Postman currently right? the issue is that you're using a live mode key, and when you're in live mode we require that you redirect to an HTTPS URL

#

so the easiest thing is to do exactly what you're currently doing, but to use your test mode or sandbox key instead

#

let me grab you a guide on how to get those

ripe fern
#

Ok

daring hollow
ripe fern
#

But then the connected account can be used as a normal connected account, right?

#

Doing payment, etc.

daring hollow
#

i'm not sure what you mean? sandboxes are basically test environments where you can create a test integration before going live

#

so yes, this would be a regular connected account, but it would only be able to take test transactions while you develop your integration

#

then when you're going live you will need to change your refresh_url and return_url to use HTTPS redirects

ripe fern
#

Ok, so I need a server/backend to go live

daring hollow
#

yep!

ripe fern
#

I can't use Postman to do that? And ignore the refresh_url and return_url?

daring hollow
#

you can use postman for testing things out if you create a sandbox account like i suggested, but if you want to go live with a full connect integration you should definitely have a backend handling things for you

tiny pelicanBOT