This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 64%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
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:
X-Algolia-Application-Id: [MY_APP_ID]
X-Algolia-API-Key: [MY_CONFIGURED_API_KEY]Troubleshooting steps already taken:
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:
X-Algolia-Application-Id: [MY_APP_ID]
X-Algolia-API-Key: [MY_CONFIGURED_API_KEY]Troubleshooting steps already taken:
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?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 40%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKA%3C/text%3E%3C/svg%3E)
@Azure Bineil ,
Welcome to Microsoft Q&A Platform!
Thank you for bringing this issue to our attention. To help narrow down the cause of the problem, could you please perform the following checks using Postman? This will help us determine if the issue is specific to Azure Logic Apps or related to Algolia.
Thank you for your response.
I’ve already tested the same API request using Postman, and it works fine with the correct API Key. The issue seems to be specific to Azure Logic Apps, as the Logic App sends a different API Key than the one configured.
Any guidance on resolving this in Logic Apps would be appreciated.
Thank you!
Thank you for your patience and for providing additional information.
Based on your feedback and further investigation, there have been reports of any extension intercepting and modifying network requests, including the x-algolia-application-id header, which could explain why Algolia is receiving a different API Key than the one configured in your Logic App.
Could you check if there are any browser extensions or security software that might be intercepting and modifying your requests. Disable them temporarily to see if the issue persists.
If the issue is resolved extensions, you can re-enable them one by one to identify the specific extension causing the problem.
The same has been discussed in the github channel. Please refer the link:
Invalid Application-ID or API key · Issue #1157 · algolia/algoliasearch-client-javascript
Hello,
Thank you for your response and suggestions. I’ll check for browser extensions or security software that might intercept requests as you recommended.
However, the GitHub link you provided leads to a "404" error, even after logging in. Could you confirm the correct link or provide more details?
Thanks again for your help!
Best regards,
My apologies for any confusion caused. It appears I may have overwritten the previous content while copying. I have now updated it for your reference. Please find the link reposted here:
https://github.com/algolia/algoliasearch-client-javascript/issues/1157
Hello,
Thank you for clarifying and sharing the correct link. I’ll review it and see if it helps resolve the issue.
I appreciate your support!
Best regards,