A tool to access each of the 'Alteryx' Gallery 'API' endpoints. Users can queue jobs, poll job status, and retrieve application output as a data frame. You will need an 'Alteryx' Server license and have 'Alteryx' Gallery running to utilize this package. The 'API' is accessed through the 'URL' that you setup for the server running 'Alteryx' Gallery and more information on the endpoints can be found at < https://gallery.alteryx.com/api-docs/>.
alterryx provides access to each of the Alteryx Gallery API endpoints.
alterryx users can:
Retrieve information on Alteryx Gallery resouces like apps, workflows, and macros
Queue jobs for applications
Retrieve the status and output of jobs
In order to use this package, you will need to have a private gallery API key and secret
Once you have obtained your API key and secret set them as global options. Though it is not necessary, it will save you typing later if you also set your Alteryx Gallery URL as an option.
alteryx_api_key <- "ALTERYX_API_KEY" alteryx_secret_key <- "ALTERYX_API_SECRET" alteryx_gallery <- "https://yourgallery.com/gallery" options(alteryx_api_key = alteryx_api_key) options(alteryx_secret_key = alteryx_secret_key) options(alteryx_gallery = alteryx_gallery)
Access to Alteryx Gallery resources like workflows, applications, and macros are managed through studios. Your account has a subscription id which determines what you can access. For the purpose of this package, when you see the term 'resource' that can refer to anything published to the Alteryx Gallery like workflows, applications, and macros. When you see 'application' or 'app' it specifically refers to files with the extension .yxwz that are published to your Gallery.
The resources you can access are obtained using
subscription <- get_app()
You now have a
list containing all of the resources you can access. If
you are a power user, this is probably going to be a long list. To pare
down the list use the
If you wanted to see only the five most recently uploaded resources, you
can use the
request_params <- list( limit = "5", sortField = "uploaddate" ) subscription <- get_app(request_params)
There is a reason to differentiate between 'resources' and 'apps'.
get_app will return all resources that you can access via your
subscription that match the search parameters. However, only 'apps' can
be used with the rest of the API functions. To make sure that
only returns apps, use
packageType = "0" as a request parameter.
request_params <- list( packageType = "0", limit = "5", sortField = "uploaddate" ) subscription <- get_app(request_params)
If you are looking for a specific app, it might be easiest to simply search for it by name. Lets say we are looking for an application named "api_tester.yxwz".
request_params <- list( packageType = "0", search = "api" ) subscriptions <- get_app(request_params) app <- subscriptions[]
In this case, the app I was looking for was the first result in the list.
If you would like to work with the application in Alteryx, you can use
doanload_app to download the application as a .yxzp file.
Now that I have the app I want, I want to queue a job for it. A 'job' is one run, a single iteration of an app.
Most of the time, applications have questions that must be answered in order for the app to run. For example, an app that performs trade area analysis might ask you to specify a radius for the trade area. These questions are set by the app author when they create the application in Alteryx Designer. My app, "api_tester.yxwz" has a single question: "How long should this application run?"
If you don't have your app questions memorized, use
questions <- get_app_questions(app)
Each question has a name and a value. In my specific case, the question name is "runtime" and the default value is "1". Because this app "api_tester.yxwz" was built specifically to test this API client, the "runtime" question will simply determine how long the app will run.
I would like the app to run for "3" minutes. Use
format the answers.
name_values <- list( name = "runtime", value = "3" ) answers <- build_answers(name_values)
If your application has multiple questions, send each as a
name_values1 <- list( name = "one", value = "1" ) name_values2 <- list( name = "two", value = "2" ) multiple_answers <- build_answers(name_values1, name_values2)
Once you have the answers to the app questions you can queue the job.
job <- queue_job(app, answers)
job will begin with status "Queued". Poll the job using
to update the job status.
job <- get_job(job)
Most Alteryx jobs contain an output tool that writes data once the job
is complete. Use
get_job_output to retrieve the results as a
data.frame. The result will be a list with one element for each valid
output. 'Valid' in this case means an output from an Alteryx output tool
that can be converted into a
A job needs to have a "Completed" status before outputs can be retrieved.
output <- get_job_output(job)
All outputs cannot be properly converted to a
data.frame. If your job
contains outputs that cannot be converted,
get_job_output will issue a
warning by default and skip the 'invalid' outputs.
In order to be properly converted, your output must be written in csv or yxdb format from the Alteryx app published to Gallery.
API functions will no longer produce an invalid signature message when using special characters (such as spaces) in parameter string
Updated client to reflect changes in Alteryx Gallery API with 2018.1 release
Updated version dependency for jsonlite as older versions of the package do
not contain the
empty_answer to streamline the process of queueing apps with no
get_info will now print less information by default to improve readability.
Added the binary parameter
full_info to print all info from the API.
queue_job can now "track" a job. If
track_job = TRUE, the function will
not return a value until the job has finished running on the Alteryx Gallery