Incorrect API Key Sent to Algolia via Azure Logic Apps

Azure Bineil 0 Reputation points
2025-01-17T18:40:36.9+00:00

Hello,
I am facing an issue with a Logic Apps workflow configured to send HTTP requests to the Algolia API. Despite setting the correct API Key and Application ID in the HTTP action headers, Algolia logs show that a different API Key is being received.

Steps to reproduce the issue:

  1. I configured a Logic App to make HTTP requests to Algolia.
  2. The HTTP action includes the following headers:
    • X-Algolia-Application-Id: [MY_APP_ID]
      • X-Algolia-API-Key: [MY_CONFIGURED_API_KEY]
      1. When the Logic App runs, Algolia logs indicate that a different API Key is sent instead of the one I configured.

Troubleshooting steps already taken:

  • Verified that the API Key in Logic Apps matches the one in the Algolia dashboard.
  • Ensured there are no dynamic parameters or variables altering the API Key.

Expected behavior: The API Key configured in the Logic App should be sent exactly as set in the headers.

Actual behavior: Algolia receives a different API Key, which causes authentication issues.

Request for assistance: How can I ensure the correct API Key is sent to Algolia without any modification? Are there any hidden settings or configurations in Logic Apps that could alter the API Key?

I am facing an issue with a Logic Apps workflow configured to send HTTP requests to the Algolia API. Despite setting the correct API Key and Application ID in the HTTP action headers, Algolia logs show that a different API Key is being received.

Steps to reproduce the issue:

  1. I configured a Logic App to make HTTP requests to Algolia.
  2. The HTTP action includes the following headers:
    • X-Algolia-Application-Id: [MY_APP_ID]
      • X-Algolia-API-Key: [MY_CONFIGURED_API_KEY]
      1. When the Logic App runs, Algolia logs indicate that a different API Key is sent instead of the one I configured.

Troubleshooting steps already taken:

  • Verified that the API Key in Logic Apps matches the one in the Algolia dashboard.
  • Ensured there are no dynamic parameters or variables altering the API Key.

Expected behavior:
The API Key configured in the Logic App should be sent exactly as set in the headers.

Actual behavior:
Algolia receives a different API Key, which causes authentication issues.

Request for assistance:
How can I ensure the correct API Key is sent to Algolia without any modification? Are there any hidden settings or configurations in Logic Apps that could alter the API Key?

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,313 questions
0 comments No comments
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.