Perform a Post API OAuth 2.0 call to get token and pass token to a GET API Basic Auth Header
I need to make a Post Rest API call using OAuth 2.0 with client_id and client_secret and then pass the token to a Get Rest API snap to make the api call Client Authentication ‘Send as Basic Auth Header’. How can I do this using the Rest Snaps?
Pagination in REST API
A very good explanation of how to implement pagination in REST API in this below blog post: SnapLogic – 4 Feb 16 REST GET and the SnapLogic Public APIs for Pipeline Executions As a part of a wider analytics project I’m working on, analyzing runtime information from the SnapLogic platform, I chose ... When I try to implement the same(I am extracting data from survey monkey api), I have noticed that when the “Next URL” is executing it is ignoring the query parameters provided.As shown in below image, when service URL is executing it’s getting right records considering all input query parameters i.e total:3043 but when “Next URL” is hitting it is extracting all records i.e. total : 61896 How to include query parameters in “Next URL” to get required data?
Smartsheet rest api pagination
Hi , We are integrating smartsheet rest api’s in snaplogic. We get only totalrecordscount in the response. there is no other things comes up in response. I need to apply pagination . In paramters i can use page and pageSize . Page is something which page we want to access and pageSize is 100 by default. These 2 paramters are not part of the response. I am not sure how I can create hasNext and nextUrl to paginate and fetch all 77k records. I am attaching the screenshots of rest snap settings .I am unable to loop. it is like never ending. please suggest. https://smartsheet.redoc.ly/tag/reports#operation/getReport offset is a parameter i gave as 0 for incrementing in nexUrl page
Rest API service endpoint returned erros result: Status Code =403
When configuring a REST Post of the mailjet API, it indicates the following message. Error: Reason: REST API service endpoint returned error result: status code = 403, reason phrase = Forbidden, refer to the error_entity field in the error view document for more details Resolution: Please check the values of Snap properties. Error Fingerprint[0] = efp:com.snaplogic.snap.api.rest.89xhsFt7 When performing the test in Postman, the execution is correct
Unexpected Rest Get snap behaviour
We have created a pipeline where we are using rest POST snap to run the job and rest GET to poll for job status until success (using has and hasNext properties). APIs are created in AWS API Gateway and both paths have IAM authorisation set. Observing some strange behaviour where sometimes the pipelines execute without any error (job run and wait till job success and continue rest of pipeline), other time returns 2 or 3* 200 responses (running state) but throws 403 error after some time [ { "error": "REST API service endpoint returned error result: status code = 403, reason phrase = Forbidden", "stacktrace": "com.snaplogic.snap.api.SnapDataException: REST API service endpoint returned error result: status code = 403\n\tat com.snaplogic.snap.api.rest.RestResponseProcessor.process(RestResponseProcessor.java:379)\n\tat com.snaplogic.snap.api.rest.RestRequestExecutor.execute(RestRequestExecutor.java:426)\n\tat com.snaplogic.snap.api.rest.RestRequestExecutor.executeOnce(RestRequestExecutor.java:323)\n\tat com.snaplogic.snap.api.rest.RestRequestExecutor.execute(RestRequestExecutor.java:190)\n\tat com.snaplogic.snap.api.rest.RestRequestExecutor.execute(RestRequestExecutor.java:173)\n\tat com.snaplogic.snaps.rest.Get.process(Get.java:152)\n\tat com.snaplogic.snap.api.ExecutionUtil.process(ExecutionUtil.java:106)\n\tat com.snaplogic.snap.api.ExecutionUtil.executeForDocument(ExecutionUtil.java:118)\n\tat com.snaplogic.snap.api.ExecutionUtil.execute(ExecutionUtil.java:81)\n\tat com.snaplogic.snap.api.SimpleSnap.execute(SimpleSnap.java:70)\n\tat com.snaplogic.snaps.rest.Get.executeForSuggest(Get.java:196)\n\tat com.snaplogic.cc.snap.common.SnapRunnableImpl.executeSnap(SnapRunnableImpl.java:807)\n\tat com.snaplogic.cc.snap.common.SnapRunnableImpl.executeForSuggest(SnapRunnableImpl.java:648)\n\tat com.snaplogic.cc.snap.common.SnapRunnableImpl.doRun(SnapRunnableImpl.java:865)\n\tat com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:436)\n\tat com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:120)\n\tat java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)\n\tat java.base/java.util.concurrent.FutureTask.run(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n", "reason": "REST API service endpoint returned error result: status code = 403, reason phrase = Forbidden, refer to the error_entity field in the error view document for more details", "resolution": "Please check the values of Snap properties.", "status_code": "error", "headers": { "content-length": "23", "content-type": "application/json", "date": "Fri, 12 May 2023 06:04:49 GMT", "apigw-requestid": "Ey6WgqeIMEMYQ=", "connection": "keep-alive" }, "error_entity": "{\"message\":\"Forbidden\"}", "request_headers": [ { "authorization": "AWS4-HMAC-SHA256 *****", "x-amz-content-sha256": "e3b0c44298fc1c149afbf4c899fb92427ae41e4649b94ca495991b7852b855", "accept": "*/*", "x-amz-date": "20230512T055934Z" } ], "statusCode": 403, "snap_details": { "label": "Get Job Status", "instance_id": "d11c3d70-02f8-45b4-a1fd-8f0a25539c15", "class_id": "com-snaplogic-snaps-rest-get", "build_tag": "main21015", "views": { "in": { "input102": { "count": 1 } }, "out": { "output101": { "count": 5 } }, "error": { "error0": { "count": 0 } } } }, "original": { "original": { "response": { "statusLine": { "protoVersion": "HTTP/1.1", "statusCode": 200, "reasonPhrase": "OK" }, "entity": { "runId": "667c5da8694a408ba44c4b8b6566b282" }, "headers": { "content-length": "131", "content-type": "application/json", "date": "Fri, 12 May 2023 05:59:29 GMT", "apigw-requestid": "Ey5VlnSoAMPSQ=", "connection": "keep-alive" } } } } } ] Found this error message in CloudWatch logs: “The request for the IAM Authorizer doesn’t match the format that API Gateway expects.” Any idea why this is happening and how to handle this case?
