ION API - Failed to Fetch

Hello,

I am tryong to creatie an API, while doing so I am facing the Error as below,

Below are teh parameters I am passing, but the curl generated is different.

The Curl : curl -X POST "">mingle-ionapi.eu1.inforcloudsuite.com/.../token -H "accept: application/json" -H "Authorization: Bearer eyJraWQiOiJrZzphY2ZhYTQ1OC05OGE3LTRkNjYtYjM4YS04MzY5NDk4NzRhZjMiLCJhbGciOiJSUzI1NiJ9.eyJUZW5hbnQiOiJKNzNDSjZSWVVFM0dXNzg4X1RTVCIsIklkZW50aXR5MiI6ImQzMDJmMTA0LTcwNTMtNDIxOC1hZTVmLWZhN2NlNjA2YTk5MiIsIlNTT1Nlc3Npb25JRCI6Iko3M0NKNlJZVUUzR1c3ODhfVFNUfmY3MzlkZjNkLWEwZTMtNDY5Zi1hNjk5LTBkZjljZTM1ODEwMyIsInNjb3BlIjoib3BlbmlkIiwiSUZTQXV0aGVudGljYXRpb25Nb2RlIjoiQ0xPVURfSURFTlRJV5MTExNjcsImlzcyI6Imh0dHBzOi8vbWluZ2xlLXNzby5ldTEuaW5mb3JjbG91ZHN1aXRlLmNvbS9pbmZvcnN0cyIsImF1ZCI6Imh0dHBzOi8vbWluZ2xlLWlvbmFwaS5ldTEuaW5mb3JjbG91ZHN1aXRlLmNvbSJ9.ScNJeTTlNXz2gnl_9GAPvCr6qJRWyk2YqXJNc9VnUkAhv2S80EQYGiVofvmONODRVVKFwRtIqPboDzigQqOOBbn022VkxbonyZGKqEnwNnWmMC6P8rteqTJN9gVJNOtvua7rkPL6aaN-CeMH5YUWsBdD2KQmqCJ9ghkRmtZevkaUrrHH0jNcYfQF1JmHMTdsrLAvQs3w7oFyb0HuaYoCS3Mn3gMuxwWTFzp9sWIwspmVqFB2UgXsyNahGVcDCW-RDSOWVUudpFmY0dIoc_1hW6LrT7Ujwvk1jQgBVGmVNYD8aeXP0sXAZtpEtiLgWHg59WPyu8aeXY9X5l95tIArnw" -d ""

As it is observed, that in Authorization parameter(header) a different value is passed, wheras the Curl generated shows a totally different value.

My Requirement is that the Value in parameter and Curl should be same and receive '200' response.

Please help me out in this situatuion.

Find more posts tagged with

General Discussions

Accepted answers

All comments

unknown

The Authorization Bearer token you see in the CURL is the token generated by the Portal, it is not the one you provided, try to copy that snippet and import in postman and you will see also your data

Ajay Dalvi

The same configuration is working fine in Postman, but in ION API I face the 'Failed to Fetch' Error in response.

unknown

can you export your suite definition from api gateway and share the input for the endpoint, if possible?

Ajay Dalvi

Okay how should I share ?

unknown

Hi,

What is the Authentication type to access the endpoint? Oauth 2.0?

If its Oauth2.0 Please try to setup the in Target Endpoint security.

Ajay Dalvi

The Type is 'No Auth', requiring a Authorization Header for a fixed value.

unknown

When you register your APIs as a suite in API Gateway, you are establishing a central point of communication for all the inbound and outbound communication with your APIs through API Gateway action as a reverse proxy server.

That means the request from client application passthrough the proxy server with OAuth2 security by default. subsequently the proxy server enforces the request polices if applicable and route the request to the target server using the target endpoint security method.

Based on your specific use case, it appears that the target endpoint security is set to anonymous or no auth with a static token provided as an 'Authorization' header parameter.

To address this, you can follow these steps:

Rename the 'Authorization' Header Parameter: Modify your Swagger document by renaming the 'Authorization' header parameter to something like 'x-authorization'.

Add a Request Endpoint Policy for Authorization: Implement a request endpoint policy of type 'transformation' within Endpoint polices. In this policy, assign the value of 'x-authorization' to the 'Authorization' header. Make sure to save these changes.

Add a Request Endpoint Policy to remove x-authorization: Implement a request endpoint policy of type 'header' within Endpoint polices. In this policy, delete the header parameter 'x-authorization' from the header. Make sure to save these changes.

Test the API

hope this help.

Ajay Dalvi

Thank you for the detailed step wise guidance but unfortunately this didn't work.

Copyright © 2025 Infor. All rights reserved.