How to send dynamic header values with the API

Jici · 2025-03-23T16:19:53.320Z

In your screenshot, you can see that you didn’t initialize your call (in red). You will need to get a valid code and paste it (really fast) to api connector and initialize your call. Once it’s done, you will be able to use it in workflows and populate this dynamically using Get data from url.

harumaki.ono · 2025-03-24T00:47:23.408Z

Thank you.
That’s it.

image1274×734 8.45 KB

image968×558 51.1 KB

Sorry, please help me a bit more.

But when I add this continue API to the workflow, an error message appears for some reason.
Do you know the cause of this?
I can share screenshots if necessary, so please let me know.

image1682×808 16 KB

The other “initAPI” issues an Auth0 login URL (authUrl).
This is opened by “Open an external website”.

image1434×1482 57.3 KB

Next, once the login is complete, redirect to the following URL:

Redirect destination: https://xxxxxx.com/api/1.1/oauth_redirect?code=XXXXXX

The “code” is returned as a URL parameter, so retrieve it here and then execute “Continue API”.

image800×708 7.99 KB

image1424×2286 93.2 KB

Next, I want to use the token obtained from the Continue API to transition to the register page (user profile registration page).

image782×900 9.34 KB

■Problem

image1044×796 25.7 KB

However, when I click the login button, a ContinueAPI error occurs.
As you can see in the screenshot above, initialization has been completed.

I would be grateful if you could tell me how to solve this problem.

■Addendum

After running this flow, I looked at the work again and it said,

This call has been modified since you last initialized; consider reinitializing.

What should I do?

image1098×548 9.64 KB

Jici · 2025-03-24T01:30:44.060Z

You have a wrong authrozation when you get the code. Use step by step to check what you get and send to api.

harumaki.ono · 2025-03-24T04:38:10.858Z

Thank you.

Sorry, I’ve tried various things but I still don’t understand.

Is it possible that in STEP 3 the code obtained from the URL is not being sent to the API?

image1176×584 10.9 KB

Jici · 2025-03-24T11:45:57.531Z

Could be two thing. A) You are not getting the code from the page url.
From what I see, this may be possible as you try to use open an external website that is probably the authorize url and after in the same workflow, you are trying to fetch the token.

You should remove all step after open an externa website (that is probably returning an error in issue checker anyway because this should be the last step in a workflow) and instead add a workflow on page load (when get code from page url is not empty) and process to the continue step.

harumaki.ono · 2025-03-24T16:09:55.613Z

Thank you.
I feel like I’m almost there.

image914×888 12.4 KB

image1268×1042 27.9 KB

I tried separating the workflows. What do you think?

However, as it is now, the page is loaded on the login page (https://xxxxxxxx.com/login), so it seems that the continue API cannot be called.

Currently, when the Auth0 login is completed, it redirects to the following:
https://xxxxxx.com/api/1.1/oauth_redirect?code=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

image1486×392 19.2 KB

What should I do in this case?

I would appreciate your advice.

Thank you for your continued support.

Jici · 2025-03-24T16:15:22.030Z

You cannot use the generic redirect url if you want to manually manage the auth process. The generic url is only used if you select the Bubble user-agent auth. You are using self-handled. You could try to use a backend WF API endpoint with redirect to a page after or just set a page of your app that will contain the continue part (can be the same page that you have the authorize link (with conditionnal that detect the code in url, you could hide button to authorize page and show a loading icon)

harumaki.ono · 2025-03-25T14:02:09.891Z

Thank you.
I apologize for the late reply.

I understand that a generic redirect URL cannot be used.

I was trying to create an API workflow, but I don’t know how to do it specifically.

This is what I have currently, but does this seem correct?

image914×1412 31.7 KB

（In particular, I have little understanding of the following workflow:）

image722×1032 15.8 KB

What exactly should I do?

I apologize for the trouble, but I would appreciate any advice you could give me.

I look forward to your continued help.

Jici · 2025-03-25T14:45:23.369Z

You don’t need to return data, you need to call your continue endpoint and do what you want with it after.
But it’s easier to just redirect the user to a page of your app with the continue action on page load like I’ve suggested before.

harumaki.ono · 2025-03-25T15:10:11.752Z

Thank you.

I’m back to the page load workflow.

If I go with the latter method, is there something wrong with the relevant part?

image1072×1036 30.9 KB

image1408×1056 29.3 KB

By the way, I think I need to set a redirect URL on the aurh0 side as well, but I’ve set the exact same one. Is this okay too?

image1440×1554 60.4 KB

Jici · 2025-03-25T15:12:20.528Z

but the page you want to redirect the user to
Let’s say you have https://yourappname.bubblesapps.io/auth

You will add two pages:
https://yourappname.bubblesapps.io/auth (for live)
and https://yourappname.bubblesapps.io/version-test/auth (for dev)

in this page, you will detect the code in the url and use the continue action.

harumaki.ono · 2025-03-25T15:40:39.273Z

I want it to eventually redirect to the register page.

https://xxxxxxxxxx.com/version-test/register

I tried setting this URL on the Bubble side first, but the redirect destination remained the same.

I also tried changing the URL on the Auth0 side, but an error occurred on the Auth0 login screen.

image1392×1022 19.6 KB

image1768×1256 57.5 KB

Jici · 2025-03-25T16:58:51.270Z

Double check your url in authorize url, auth0 and api connector. All of them need to match

harumaki.ono · 2025-03-29T03:42:42.780Z

Sorry for the late reply.

Thank you.

Yes, both the Auth0 Callback URLs and the Bubble redirect_uri are set to
https://xxxxxxxxxx.com/version-test/register.

Excuse me, what was the authentication URL again?

Jici · 2025-03-29T03:44:56.150Z

The one that send the user to the auth page. This end by /authorize in your screenshot. This url.often have the redirect url too. This need to match what is allowed in oauth0

harumaki.ono · 2025-03-30T13:48:54.644Z

Since it is set to https://login.xxxxxxxxxx.com/authorize?response_type=code&client_id=eEDFUYV9NvuxTI24plpaPg1iCkTpKfwi&redirect_uri=https%3A%2F%2Fxxxxxx.com%2Fapi%2F1.1%2Foauth_redirect&scope=openid+profile+email

, it seems that https://xxxxxxxxxx.com/version-test/register is not included.

How can I do this?

Do I need to set it up somewhere in Auth0 or Xano?

I don’t know where to set it up.

Jici · 2025-03-30T15:18:15.548Z

If you are doing manual auth, you should have an action like open an external website? This is where you set that,in Bubble.

harumaki.ono · 2025-04-01T13:38:54.253Z

Thank you.

So some settings are required to authenticate manually.

Where is this external site?

What do I need to open to authenticate?

Also, is the flow complicated…?

I’m also considering allowing users to log in with their regular email address and password in some cases.

I apologize for the trouble, but I would appreciate any advice you could give me.

Jici · 2025-04-01T13:53:34.740Z

Did you set this yourself or do you use a plugin? The open an external website I’m talking about is an action in Bubble…

harumaki.ono · 2025-04-01T15:21:28.229Z

No, I don’t remember setting /authorize myself.
I looked it up and found the following in Xano’s initAPI. Does this seem related?

image2572×1412 97.6 KB

Xano

Auth0 | Xano

Discover how to integrate Auth0, a powerful authentication solution, into your Xano applications without writing code. Learn about Auth0's features like social logins, multi-factor authentication, and customizable login widgets. Follow the...