Forum Discussion
Thank you @tlikarish
I made the changes as you suggested but I am still getting error:
here is the pipeline property i have :
Error I am getting:
Failure: REST API service endpoint returned error result: status code = 400, Reason: REST API service endpoint returned error result: status code = 400, reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details, Resolution: Please check the values of Snap properties.
Not sure what I am missing. ๐
Hi RavNeu,
Did you ever figure out why you received the error?
Failure: REST API service endpoint returned error result: status code = 400, Reason: REST API service endpoint returned error result: status code = 400, reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details, Resolution: Please check the values of Snap properties.
- joel_bourgault3 years agoNew Contributor III
Hi All,
Just to share my experience: to retrieve runtime statuses, I use the following endpoint:https://elastic.snaplogic.com/api/1/rest/public/runtime/%1$s?last_hours=%2$s&limit=%3$s&offset=%4$s
, that I call.sprintf()
on it with following variables:-
%1$s
is replaced by my Org -
%2$s
is replaced by a number of hours from now in the past -
%3$s
and%4$s
are used by pagination
This is associated with my personal account, stored as REST Basic Auth account.
Hope this helps!
- jjenkins13 years agoNew Contributor
Hi
I did see your message and wanted to say, โThank you!โ
-