web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / custom connector - api...
Power Apps
Unanswered

custom connector - api key in header - always returns 401

(0) ShareShare
ReportReport
Posted on by 12
Hi All,
 
I am trying to connect a PowerApp to an Appian app via a custom connector and it just isn't working. At this stage just using GET.
 
I set up the Appian api side correctly. How do I know? I've tested in Postman, using cURL.
I also created a power automate flow that is returning data to my PowerApp. I just want to replace the flow with a custom connector - sounds easy right?
 
 
Like all MS/Power Platform products, I'm sure there's some special case where this connector needs to be set up a little differently - or maybe it will suddenly start working in a weeks time even though nothing has been changed.
 
These are the options I have tried, based on reading so so many articles and similar questions. Instead of modifying an existing set up, I created multiple connectors as it didn't seem to update properly/fast enough for how I test.
  • Filling out the Security section - when creating the connection, I add the api key.
 
  • Filling out the Security section - but using Authorization as the parameter and adding Bearer <key> during connection creation
 
  • Filling out the Security section - but using Authorization as the parameter AND using a Policy: Set HTTP header template, Authorization as the Header name, Bearer <key> as the Header value
 
  • Filling out the Security section- but using Authorization as the parameter AND using a Policy: Set HTTP header template, appian-api-key as the Header name, <key> as the Header value
 
  • Not filling out the Security section - using custom header instead
 
  • Not filling out the Security section - using a Policy: Set HTTP header template, Authorization as the Header name, Bearer <key> as the Header value
  • Not filling out the Security section - using a Policy: Set HTTP header template, appian-api-key as the Header name, Bearer <key> as the Header value
Every single time I get:
 
What am I doing wrong?
 
I successfully create a custom connector to themoviedb and created a powerapp and was able to show all data via a search query, so I know it can be done.
 
If my powerapp works with a different custom connector and also works with a flow to my actual data, I just dont know where to go from here. Any help is appreciated.
Categories:
I have the same question (0)
  • Suggested answer
    Jon Unzueta Profile Picture
    1,827 Super User 2025 Season 2 on at
    Hi @rudev

    It sounds like you've tried a lot of different approaches to get your custom connector working with Appian. Here are a few troubleshooting steps and best practices that might help resolve the issue:

    1. Check API Endpoint Configuration: Ensure that the API endpoint in your custom connector is correctly configured. The path should be relative to the host of the API you're trying to reach.

    2. Authentication Methods: Since you've tried various methods, make sure the authentication type matches what the Appian API expects. If using API Key, ensure it's correctly set up in the Security section. For OAuth 2.0, verify that the redirect URI is correctly configured.

    3. Connector Updates: Sometimes, changes made to custom connectors don't reflect immediately in PowerApps. Try removing the connector from your app and re-adding it to ensure the latest updates are applied.

    4. Error Handling: Implement error handling in your connector to catch and diagnose issues. Use IfError() to manage API failures and log detailed error messages.

    5. Testing in Power Automate: Since your flow works, compare the configuration of the flow with your custom connector. Ensure that all headers, parameters, and authentication methods match exactly.

    6. Custom Headers: If the Appian API requires specific headers, ensure they are correctly set in the custom connector. Using policies to set HTTP headers can be effective, but make sure the header names and values are accurate.

     

    If the response is helpful to you, a like or mark as the correct solution. thank you so much!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 711 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 319 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard