I need some help with the Orchestrator API/HTTP request activity
I recently started at a new company, and is rebuilding my “create a new project”-process.
Along with some other features, this process also creates Orchestrator queues for the new project.
At my old company, I created this feature using the standard HTTP request activity to authenticate and post the queue.
Now I need to recreate it i’m using the Orchestrator HTTP Reuqest activity instead of the normal one.
Asking for what queues is currently in orchestrator is working fine, but when trying to manipulate the queues i get an 403 “You are not authorized” StatusCode. This goes for both Post and Delete (with the associated changes to the input).
- Isn’t it the whole idea with the Orchestrator HTTP activity that it automatically authorizes me?
- Since I can get the queues I assume it does, but then why can’t I manipulate them?
When logging into orchestrator through the web interface, I can both Create and delete queues from the same user account that the robot uses, so i know it’s not a problem with access control for the user in orchestrator.
I could probably recreate it using the normal HTTP request activity, but I want to know why this isn’t working, since it would be a lot easier not needing to authendicate whenever i need to use the API
- Is it correct that the API guide have not been updated since 2016.2?
Any help will be appriciated!