HI @Mehul Ramani my requirement is below . based on the flow available, to get the token based on the flow that pierre share we are using invokehttp and then capturing the token. ( the access_token attribute is right ?) after that flow we can pass the token to another invokehttp processor to get the jason and do further processing . Since I am bit new to this , have confusion in parameter setting . did you used any specific parameter and attributes to pass token . below is my requirement - sorry for this long post , The APIs are all accessed via REST invocations and return results in JSON format. The API use the OAuth 2.0 standard to authenticate all requests To authenticate to the API endpoint, we will need a token we send with every API call. To retrieve a token please follow the steps below- Request an access token by sending your Client ID and Client Secret via HTTP Basic Authentication, using an HTTP POST request. The Client ID and Client Secret need to be encoded to Base64, using the UTF-8 character set, in the form of client_id:client_secret. A resource you can use for this purpose ishttps://www.base64encode.org/. This string is then passed as the Authorization header. The API will respond with an access token Note: Tokens are only valid for one hour. After one hour a new token is required. Pass the token as the Authorization header to access the API resources: API resource data is returned: ... View more

@Mehul Ramani Hello , would you be able to guide me on how you proceed with the solution and flow. thx much ... View more

@ pierre Villard - Hi- I went thru your article posted in below link - https://pierrevillard.com/2016/04/12/oauth-1-0a-with-apache-nifi-twitter-api-example/ In our API guide , I found that API uses use the OAuth 2.0 standard to authenticate all requests The APIs are all accessed via REST invocations and return results in JSON format. The API use the OAuth 2.0 standard to authenticate all requests To authenticate to the API endpoint, we will need a token we send with every API call. To retrieve a token please follow the steps below- Request an access token by sending your Client ID and Client Secret via HTTP Basic Authentication, using an HTTP POST request. The Client ID and Client Secret need to be encoded to Base64, using the UTF-8 character set, in the form of client_id:client_secret. A resource you can use for this purpose is https://www.base64encode.org/. This string is then passed as the Authorization header. The API will respond with an access token Note: Tokens are only valid for one hour. After one hour a new token is required. Pass the token as the Authorization header to access the API resources: API resource data is returned: I assume there were some more steps needed in between which is missing to make the correct flow. Can you please guide ... View more

@ pierre Villard - Hi- I went thru your article posted in below link - https://pierrevillard.com/2016/04/12/oauth-1-0a-with-apache-nifi-twitter-api-example/ In our API guide , I found that API uses use the OAuth 2.0 standard to authenticate all requests The APIs are all accessed via REST invocations and return results in JSON format. The API use the OAuth 2.0 standard to authenticate all requests To authenticate to the API endpoint, we will need a token we send with every API call. To retrieve a token please follow the steps below- Request an access token by sending your Client ID and Client Secret via HTTP Basic Authentication, using an HTTP POST request. The Client ID and Client Secret need to be encoded to Base64, using the UTF-8 character set, in the form of client_id:client_secret. A resource you can use for this purpose is https://www.base64encode.org/. This string is then passed as the Authorization header. The API will respond with an access token Note: Tokens are only valid for one hour. After one hour a new token is required. Pass the token as the Authorization header to access the API resources: API resource data is returned: I assume there were some more steps needed in between which is missing to make the correct flow. Can you please guide ... View more

@pierre Villard I did added the generate flow file and did see that stats are updating - till split jason processor. after that there was no change in processor. I am not able to debug the issue . can you suggest how to debug. What best practices we should follow to do error handling ... View more

I did this and see the task and time is increasing but no change in bytes. I used POST method because I saw the following . Does any property on header needs to be set Request an access token by sending your Client ID and Client Secret via HTTP Basic Authentication, using an HTTP POST request ... View more

@Pierre Villard i did try this using the below flow and added at the last put file but still struggling with the flow ... View more

@pierre Villard thanks for your reply . I made the below flow above for split jason and then use the below for evaluate jason path after running i am not able to see any progress . ... View more