<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Error Executing the Raw Request Card in Workflows when Passing an Authorization Header
Workflows
Okta Classic Engine
Okta Identity Engine
Overview

When using the workflow API Connector Raw Request card (or the other API Connector action cards) and passing an Authorization header in the request, one of the following errors may occur:

  • 401 Unauthorized
  • 403 Forbidden
  • 400/500
Applies To
  • API Connector cards - Raw Request, Get, Post, Put, Patch, and Delete
  • Passing the Authorization header inline in the Raw Request card
Cause

If the Authorization header is configured and formatted properly in the Raw Request card and it works when calling the API outside of Workflows using a tool like Postman, the Raw Request card may be configured to use a connection with an Auth Type that overrides the Authorization header. The configured Auth Type for the selected connection will be used instead of the inline Authorization header. The error code and error message will vary depending on the Auth Type used by the selected connection.

Solution
  1. Create a new API connection that uses an Auth Type of None.
    API connection that uses an Auth Type of None  

  2. Use the new connection in any API Connector action cards that need to pass the Authorization header directly in the request.


Related References

Loading
Error Executing the Raw Request Card in Workflows when Passing an Authorization Header