Hi Tim,

The issue is your token is not passed correctly & hence you are getting 401.

For token-based authentication, use the "OnBeforeRequest" callback to add the required HTTP authorization header to the outgoing requests. Check Simple Customizations for more information

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/REST/Consume_REST_APIs/Simple_Customizations

Hi, 

I agree with Assif that your passing parameter is not correct. You can share your oml file so we can check and validate and can able to upload the working version for you.

Thank you,

Sudip

Thanks everyone for the suggestions.  Here is a screenshot and I have attached the oml file.

Hi Tim, 

I don't think your issue is with OutSystems. I tried the exact same POST in Postman and got the same error. Are you sure that you have the correct key. Aren't there any typos?

I just tried in Postman and it worked fine.  Here is the CURL which can be imported in Postman via the import button top left and then paste raw text:

curl --location --request POST 'https://stevesie.com/cloud/api/v1/endpoints/e7762587-1426-47ac-b5d5-d9b2836ec89b/executions' \
--header 'Token: 3138c6bb-6623-4bef-9da0-c61793a0d117' \
--header 'Content-Type: application/json' \
--data-raw '{"inputs":{"neighborhood_id":"","ne_lat":"","ne_lng":"","property_type_id":"4","sw_lat":"","sw_lng":"","checkin_date":"2020-5-1","checkout_date":"2020-5-28","location":"east palo, CA","price_max":"","price_min":"","superhost_only":"","currency":"","limit":"","offset":"","airbnb_api_key":""},"proxy":{"type":"shared","location":"nyc"},"format":"json"}
'

I found the issue. The have named the header in OutSystems differently then in Curl/Postman. 

In Curl the header that contains the api key is called: Token
In OutSystems the header that container the api key is called: Authorization

Change the name in OutSystems to the correct value and I'm sure it will work. 

Hi Tim,

Vincent is right, the header was incorrect.

On top of that, OutSystems needs to generate a structure for the Request Body following the Task Execution instructions of the API. After adding the specified JSON for the Request Body, I got a Status 200 OK.

I added your corrected OML as an attachment.

Regards,

Nordin

Tim,

Don't forget to get a new API key. The one you provided is now out in the open for all to use.

Thanks and I will change the API key.  OK so I too got it working in the Rest builder using the Test button.  I am new to Outsystems and am wondering how I can get this working on a page and have it show the JSON?  Im not sure why I'm getting an error below and if I should put the token, content type in the fields below on the right.  Also not clear if the Request field should have the JSON from the Request body?  Ultimately this is my first time doing a REST call as I'm learning OutSystems. Im trying to have a page display the returned JSON in a text box and then will build on that learning.  Any suggestions are appreciated.

You get this error because you input a text/string ("bbbb") but the Request parameter is of a structure type (as can be seen by de > icon before it's name). Make sure you supply the correct data type and it should work as expected.

Hello - I'm a few weeks into OutSystems. I have an issue similar to the topic of this forum thread. I have been trying to work with the ZOHO Mail API. Everything runs smooth until the point where I have to pass two headers to a GET request.  As usual, it works great in Postman, but fails to work in OutSystems. 

I reached out to ZOHO and they got back to me on two requests that I sent around the same time from Postman and from OutSystems. The Authorization header was received on the ZOHO end from Postman, but the exact same token when used from OutSystems was not received. 

The nature of the ZOHO Authorization header is a bit different from the standard "Bearer <access_token>" pattern.

Instead, the token is passed in the following pattern: "Zoho-oauthtoken <zsupp_Access_Token>" 

Here are the log extracts from OutSystems when the Service runs. I can see the token going into the Server Action, but the logs have redacted what is actually being passed in the Authorization header that makes it difficult to troubleshoot the issue.  Here are the logs snippets:

/* I can see the token being composed correctly before the actual REST API is invoked */

Zoho-oauthtoken  1000.e575cb655391706251202e8e8e8ffcb8.2966c55a90984226296e23b001ac0876

/* The redacted line in OutSystems log isn't actually helping to show what was actually passed in the Authorization. ZOHO confirmed that the token was not part of the request */

GET http://mail.zoho.com/api/accounts/6450907????????????/messages/search?searchKey=subject%3aPAYBILL%3a%3asender%3amyserviceaccount%40gmail.com&receivedTime=20160&start=1&limit=1&includeto=true HTTP/1.1

User-Agent: OutSystemsPlatform

Authorization: [redacted]

scope: messages

HTTP/1.1 400 

Connection: keep-alive

X-Content-Type-Options: nosniff

X-XSS-Protection: 1

Content-Length: 119

Content-Type: text/html;charset=UTF-8

Date: Sat, 11 Dec 2021 19:04:34 GMT

Set-Cookie: fc2f5e4ce1=e30668dc42df6294320bb6301d6073f1; Path=/,zmcsr=0efa9443-2158-4083-ba3f-0e8341f81d48;path=/;SameSite=None;Secure;priority=high,_zcsr_tmp=0efa9443-2158-4083-ba3f-0e8341f81d48;path=/;SameSite=Strict;Secure;priority=high,JSESSIONID=2E063DCF22C64BAAE993F2B66B908C6C; Path=/; Secure; HttpOnly

Server: ZGS

Pragma: no-cache

Cache-Control: private,no-cache,no-store,max-age=0,must-revalidate

Expires: Thu, 01 Jan 1970 00:00:00 GMT

X-Frame-Options: SAMEORIGIN

/* This is the error returned. It confirms that the access token was not submitted via the OutSystems HTTP request */

{"data":{"errorCode":"INVALID_TICKET","moreInfo":"Invalid ticket"},"status":{"code":400,"description":"Invalid Input"}}

Can someone help me figure out where I'm going wrong? I've consumed other APIs that are more complex in terms of the request structure, but they all accept the access token as "Bearer".  The ZOHO request on the other hand is really simple in nature, but the access token being passed in follows a different pattern.

Could this be the problem?

thanks!