Skip to main content

"This HTTP Request Action's URL did not match any of this credential's supported domains/URLs." Error

Understand the "This HTTP Request Action's URL did not match any of this credential's supported domains/URLs." error.

Angie Ruhstorfer avatar
Written by Angie Ruhstorfer
Updated yesterday

Overview

When executing an HTTP Request action that requires authentication, you may run into the following error:

This HTTP Request Action's URL did not match any of this credential's supported domains/URLs.

Cause and solution

The "This HTTP Request Action's URL did not match any of this credential's supported domains/URLs." error message is directly tied to the URL value being passed in the HTTP Request action and the used Credential's URLs and Domains setting.

Cause one: Incorrect credential usage

The credential that is being used in the HTTP action is not the correct credential to authenticate the HTTP call.

🟢 Solution: Ensure that you are using the appropriate credential relevant to the HTTP action you are attempting to execute. To avoid this, we recommend naming your credentials so that it is easy for you and your team to identify which platform they are intended for.

Cause two: Invalid credential URLs and Domains configuration

The credential's URLs and Domains setting is formatted incorrectly or contains the wrong values.

🟢 Solution: Ensure that the URLs, domains, and server hosts passed in the configuration align with the setting's supported syntax. If you have multiple values, make sure that they are space-separated within the URLs and Domains setting.

Troubleshooting checklist

☑️ Verify you are using the correct credential for the HTTP action you are executing.

☑️ Verify that the credential's URLs and Domains setting is configured correctly.

Need further assistance?

Have questions or still seeing the error after working through the sections above? We are happy to help!

⬇️ Contact Tines Support with the information below:

ℹ️ General Information:

  • Describe the behavior in detail, including steps to replicate (we recommend providing this information via a screen recording).

  • The time and date of the reported behavior.

ℹ️ Story Details:

  • The impacted story's URL.

  • The impacted credential's URLs and Domains value(s).

  • The impacted HTTP Request action's:

    • ID: Click on the action tile within your story; its ID is located at the end of the browser URL.

    • Configuration: You can copy and paste actions into a code block; this will provide the configuration of the action(s) in JSON format so that Tines Support can view it within our test environments.

Did this answer your question?