- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
06-10-2020 12:11 AM
06-11-2020 05:48 AM
Hi,
I would check to ensure that the user has sufficient access in the EPM console and is not in a limited role such as a read-only set admin. Also, have you first authenticated to use the API calls with either the EPM or Windows authentication API commands? Are you able to share the specifics of your API call, such as the URL? Remember to sanitize any corporate or sensitive information when sharing this sort of information.
09-11-2020 10:25 PM
I was getting the same error and realized I needed to add "basic " before the EPM token in my Authorization header value. It is noted very subtly in the API documentation:
Authorization
Token generated in the EPM authentication API
Type: String
Valid value: basic <Token>
Mandatory: Yes
Once I added the "basic " before the token the API call worked.
08-24-2021 07:24 AM
Hi, I am getting the same error even after adding basic before the token value and passing this as header. I am calling the API inside a powershell script. Could you please let me know exactly how the header was passed to fix this issue?
11-15-2021 01:34 AM
Got same issue at a customer onPrem installation v11.5.2
11-15-2021 05:18 AM
Hi,
To confirm, have you first successfully received the Authorization Token from performing an Authentication Request? Which Authentication Request are you using (EPM or Windows Authentication)? I recommend trying to re-create the API Request in Postman to troubleshoot. It's got a nice "Code" feature which can output the Postman request in another language - Powershell is an available option.
11-15-2021 05:38 AM
Hi
Yes in this example its an AD-integrated EPM server and API logon with Windows Authentication Request. Able to get a Authorization Token. Using exactly this token with "VFUser" to GET e.g. /EPM/API/Sets results in this error EPM000004E
Or to be more specific GET /EPM/API/Sets with only the VFUser Header + Token results in HTTP 401 and GET /EPM/API/Sets with the VFUser Header + Token and Authorization Header + Basic BASE64-Cred results in error EPM000004E
11-15-2021 06:34 AM
Hi,
When using the Windows Authentication and passing the Authorization Token for subsequent Requests, we'll need to use the VFUser parameter and using only the Authorization Token (no need for "basic" to be included). See if you can first recreate the Requests in Postman. If it succeeds there, you can export it in your choice of scripting language.
11-15-2021 06:49 AM
Hi khuan
Thanks for you response. So every request will need a valid Windows Auth (NTLM...) - I see, that explains a lot. Able now to request /EPM/API/Sets with the provided VFUser token.
Irritating was, that Basic Auth with Authorization Header + Basic BASE64-Cred did create a VFUser token on https://<EPM_Server>/EPM/API/<Version>/Auth/Windows/Logon
Thanks a lot
05-08-2025 08:50 PM
Hi,
I am getting the same error as follows, whenever I try to create a user.
EEPM00000EE: The requested resource could not be found , or the user does not have permissions for this resource.
I am using API key for authorization with "basic {{epmToken}}".
EPM version: 25.4.0.4668
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

