401 Unauthorized Error when Configuring Scheduler for /wakeup API Endpoint

[WildfootW]

Description

I am encountering a 401 Unauthorized error when trying to configure the scheduler (Cron-job) to invoke the /wakeup API endpoint, as per the last instruction in the deployment guide.

Steps to Reproduce

1. Modified the render.yaml file as per the deployment instructions.
2. Successfully created a new instance on Render's blueprint using the modified render.yaml.
3. Received the service URL and appended /callback to construct the webhook URL.
4. Pasted the webhook URL into the LINE Webhook URL section on LINE Developers.
5. Attempted to configure the scheduler to invoke the /wakeup API endpoint.

Expected Behavior

The scheduler should successfully invoke the /wakeup API endpoint without authorization issues.

Actual Behavior

Received a 401 Unauthorized error when the scheduler tried to access the /wakeup API endpoint.

Possible Causes/Suggestions

• Is there a specific format or additional requirements for the API_ACCESS_TOKEN?

[yujunkuo]

Hi @WildfootW ,

To resolve the authorization issue, please follow the steps below:

1. Configure the Environment Variable on Render Service:

• Add a new environment variable named API_ACCESS_TOKEN to your Render service.
• The value of this environment variable can be any string, for example, abc123.

2. Set the Header in Scheduler's Request:

• Add a new header named API-Access-Token to your scheduler's request.
• Set the value of this header to match the one used in the API_ACCESS_TOKEN environment variable, in this case, abc123.

By implementing these changes, the scheduler should be able to successfully invoke the /wakeup API endpoint without encountering authorization issues.

I apologize for the oversight in providing these instructions initially. If you have any further questions or encounter any issues, please feel free to reach out. Thank you for bringing this to my attention.