Getting error while configuring with postman.

Cognitonic

Hi team,

I’m trying to configure and test the OpenText API using Postman, but I’m encountering an authentication error during setup or request execution. Even though I’m able to successfully generate the access token in the Authorization tab, when I send a request to the server, I receive the following error response:

{  "type": "https://tools.ietf.org/html/draft-nottingham-http-problem-07",  "title": "401 UNAUTHORIZED",  "status": 401,  "detail": "Full authentication is required to access this resource",  "traceId": "7a7b2406b5ead78db20e48566f01e0d5"}

Could you please help me understand why this error is occurring even after obtaining the access token, and suggest how to properly authenticate step by step and access the documents through Postman?

AbelJM

Hi @Cognitonic

The most frequent reason for this 401 error, even after successful token generation, is that the Access Token is not being included, or is included incorrectly, in the HTTP Authorization header; Just double check and make sure it's placed in the Headers tab.

But if you find direct API calls in Postman cumbersome for repetitive tasks, or if you need to integrate OpenText into other business processes, you should take a look at the https://showcase.answermodules.com/what-is-module-suite/ OpenText cloud/on-premise certified.

The module abstract away the low-level authentication details, providing a much easier way to:

• Manage Documents: Simplified functions for uploading, downloading, and searching documents.
• Handle Workflows: Direct access to OpenText business process management tools.
• Ensure Compliance: Built-in tools often handle security and compliance checks required by the platform.

This can be a more robust and sustainable method for integrating with OpenText over time, especially within enterprise environments.

Let me know if this help you!