Hi,
Has anyone tried to configure Alteryx Designer to run the PUT Method against this API?
PUT ... /api/v2/analytics/reporting/schedules/{ScheduleID}
The Payload provided along with the API is the same as for the POST method. The PUT Method updates the report assigned to the provided Schedule ID when the provided json request body is modified.
I test in Postman before configuring Alteryx. In Postman, the Authorization tab for Genesys Reporting Analytics is vastly different than with other Genesys API calls as one has to provide a Callback URL, Auth URL, Access Token URL. Grant Type is "Authorization Code".
Just wondered if anyone has managed to design this API into an Alteryx workflow. It's not as likely the Alteryx Community would have an answer.
I haven't heard of Alteryx before, but the API you mention uses the same OAuth authorization mechanism as nearly all of the other endpoints in the Genesys Cloud Platform API. Are you having a specific problem for which you can share details or just seeking general advice on using Alteryx?
Hi Tim
Seems I cannot post a screen shot so I'll write in how I have to configure Postman's Authorization tab to make the PUT method work:
Access Toke: Available Tokens
Header Prefix: Bearer
Token Name: genesysToken
Grant Type: Authorization Code
Callback URL: https://oauth.pstmn.io/v1/callback
Auth URL: ... /oauth/authorize
Access Token URL: ... /oauth/token
Client ID: ####
Client Secret: ####
Client Authentication: Send client credentials in body
If I do not provide the above configuration, Postman will not update the json for the report in question. Again, a robust JSON request body is provided.
The goal is to run an Alteryx workflow on a schedule that provides updated JSON using that PUT method. Translating that Postman config into Alteryx is the kicker.
Thank you,
Chris
All of that configuration is expected as Postman is performing the authorization steps for you, so it needs those details. If Alteryx has documentation on configuring it for an OAuth2 flow, it should be very similar to Postman as our OAuth implementation adheres to the RFC spec.