Next.js sample doesn't seem to include access token in API call

[sinking-point]

Checklist

• I have looked into the Readme and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

https://github.com/auth0-samples/auth0-nextjs-samples/blob/main/Sample-01/app/external/page.jsx#L18

This is just a plain fetch with no headers set. The file indicates the access token is supposed to be included in the Authorization header.

Reproduction

N/A

Additional context

No response

[alextongdo]

I believe you are misunderstanding how this fetch works. It fetches /api/shows on the Next JS server, which is not yet the external API. The code in app/api/shows/route.js handles that request and makes the request to the external API living at port 3001, which includes the header Authorization: Bearer ${accessToken}.

https://github.com/auth0-samples/auth0-nextjs-samples/blob/main/Sample-01/app/api/shows/route.js

[50bbx]

Isn't the /api/shows fetching again /api/shows in an infinite loop? Where is the list of shows coming from?

[sinking-point]

@alextongdo thanks, you're right. I did misinterpret it. Still, it would help if this were made clearer. The text of the web page makes it sound like the external API is being called directly from the client. In any case, an example of an external API call from the client would be helpful.

[sinking-point]

@50bbx there's an API route that is part of the Next app and there's another external API too. The client calls the Next API route which calls the external API. No recursion.