After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
REST Tenant
The tenant API allows you to get information about configured tenants on your deployment. Multi-tenancy is only supported for on-premises deployments of Splunk SOAR.
/rest/tenant
Get information about the tenants configured on the deployment.
For information on configuring multi-tenancy, see Configure multiple tenants on your Splunk SOAR (On-premises) instance.
Syntax
https://<username>:<password>@<host>/rest/tenant
GET
Get a list of all configured tenants.
Example request
Get a list of tenants, using paging parameters.
curl -k -u username_password https://localhost/rest/note?page_size=5&page=0 -G -X GET
Example response
A successful GET will return a 200 response, and a JSON formatted list of tenants.
This example has multi-tenancy turned on, but only the default tenant is configured.
{ "count": 1, "num_pages": 1, "data": [ { "id": 0, "name": "Default", "description": "This is the default system tenant.", "contact": "contact name", "disabled": false, "slas": { "high": 60, "medium": 720, "low": 1440 }, "executive_approvers": null, "sla_expiry_warning_in_mins": null, "environment_variables": {} } ] }
REST Lists | REST Note |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.0.1, 5.1.0, 5.2.1, 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2, 6.3.0
Feedback submitted, thanks!