After requesting API token getting error 401: "Authorization has been denied for this request."

After requesting the REST API access token in Swagger and attempting to authenticate, what can cause the error "401 Authorization has been denied for this request"?

May 10, 2023
Knowledge

Title

URL Name

all-swagger-and-rest-api-methods-fail-after-authenticating

Article Number

000206872

Environment

Product: MOVEit Automation, MOVEit Transfer Versions: All Supported Versions OS: All Supported Platforms Other: REST API

Question/Problem Description

A user is able to successfully request an API auth token, but when using any of the API calls after authenticating, they are receiving one of the below error messages:

Server response: 401

Response body:

{
  "message": "Authorization has been denied for this request."
}

Response body:

{
  "title": "Authentication Error",
  "status": 401,
  "detail": "Invalid bearer token"
}

Steps to Reproduce

1. Open Swagger in a browser. 2. Generate an authorization token and copy it. 3. Click the Authorize button. 4. In the Value field, paste just the authorization token. 5. Click Authorize. 6. Try to use a "Try it out" option for one of the API calls.

Clarifying Information

Error Message

From Swagger for MOVEit Transfer: Code: 401 Error: response status is 401 Response body: { "message": "Authorization has been denied for this request." } From Swagger for MOVEit Automation: Code: 401 Error: Response body: { "title": "Authentication Error", "status": 401, "detail": "Invalid bearer token" }

Defect Number

Enhancement Number

Cause

This is most commonly due to not entering the word "Bearer" before the access token. It can also occur if the full access token was not pasted in, if additional characters were accidentally entered, or if an invalid token was entered.

Resolution

Ensure that the word "Bearer" is entered and that the correct access token value is pasted after it. Make sure no extra characters have been added such as quotation marks, spaces, etc.

In Swagger, this value is entered after clicking the "Authorize" button on the top right of the screen.

Note: after clicking the "Authorize" button in the authorization window, the padlock symbol will always change to appearing locked no matter what is entered in the authorization Value field, even if an invalid value was entered.

Additionally, Please see the steps below for information about how to review and update the timeout duration for tokens:

Check the location: X:\Program Files\MOVEit\MOVEit Automation Web Admin\Tomcat\webapps\ROOT\WEB-INF\classes
Locate the Config properties file.
Open the file using Notepad or Notepad++
Alter the session timeout value for access token and save.
Restart Automation services (this includes the MOVEit Automation Web Admin service).
Refer to the screenshot as reference:

Workaround

Use Postman or another application to use the REST API and to try using the access code to authenticate. This will help indicate where the issue is occurring. Additionally, if this is only an issue for one user (i.e. exception), can clone said user & delete the original as this has been successful in at least one prior instance.

Notes

Progress article(s):
MOVEit Automation - REST API Swagger User Interface
Transfer - Swagger User Interface
Swagger Try It Out options do not respect a Virtual Directory Setup for Transfer
How to troubleshoot the MOVEit REST API

Keyword Phrase

Last Modified Date

6/3/2026 10:31 PM

After requesting API token getting error 401: "Authorization has been denied for this request."

Files(0)

Was this article helpful?

Was this article helpful?

After requesting API token getting error 401: "Authorization has been denied for this request."

Information

Related Articles