Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Create Personal Access Token
  • List Personal Access Tokens
  • Optionally Include Personal Access Tokens on Read/List User Payloads
  • Revoke Personal Access Token
  • Agents

    Agent Clusters

    Audits

    Bundles and Promotion

    Bundles

    Promotion

    Business Services

    Calendars

    Cluster Nodes

    Connections

    Credentials

    Custom Days

    Groups

    Monitoring

    OAuth Clients

    OMS Servers

    Passwords

    Personal Access Tokens

    Properties

    Reports

    Scripts

    Server Operations

    System

    Task Instances

    Tasks

    Triggers

    Universal Event

    Universal Event Templates

    Universal Templates

    Users

    Variables

    Virtual Resources

    Workflow Task Instances

    Workflow Tasks

    ...

    Method

    Description

    GET

    Retrieves records from the Controller database.

    POST

    Creates, or performs an action on, a record in the Controller database.

    PUT

    Modifies a record in the Controller database.
     

    Note
    titleNote

    PUT, by itself, actually replaces an existing record with whatever information you include in the PUT operation. If you include only partial record information in a PUT, the record in the database will then contain only that information.

    In order to modify information in a record and retain all of its unmodified information, you must first GET the record from the database, modify (add/delete/change) information in the record, and then PUT the record back in the database.


    DELETE

    Deletes a record in the Controller database.

    Authentication 

    Universal Controller requires Web Service requests to be authenticated using one of Basic Authentication or Personal Access Token Authentication.

    For Basic Authentication, use the following Authorization header, where the username:password is base64 encoded.

    Access to the Controller requires basic HTTP authentication over HTTPS.

    The following methods are used:

    ...

    Panel

    Authorization: Basic username:password

    For Personal Access Token Authentication, use the following Authorization header.

    Panel

    Authorization: Bearer access-token

    While it is recommended you use the Authorization header, if required, you can alternatively pass the Personal Access Token using the access_token query parameter.

    Panel
    http://hostname:port/uc/resources/task?access_token=access-token&taskname=MyTask

    Request Limits

    You can implement application- and user-level concurrent request limits to control how many web service API requests can be in progress at the same time via the following Universal Controller system properties:

    Web Service Application Concurrent Request Limit

    Controls the number of concurrent requests for the application (that is, the Universal Controller server).

    This application-level concurrent request limit cannot be less than 1 or less than the user-level concurrent request limit (if specified).

    Web Service User Concurrent Request Limit

    Controls the number of concurrent requests per unique user ID.

    This user-level concurrent request limit cannot be less than 1 or more than the application-level concurrent request limit (if specified).

    If the application-level concurrent request limit is exceeded, an HTTP Status of 429 /Too Many Requests will be returned.

    ...

    If either restriction is in place, the following error message will be written to the Audits table and the opswise.log file when you attempt to access the RESTful Web Services API:

    Panel
    User <your user name> not permitted to use Web Services. Please check with your administrator.

    To remove the restriction, the system administrator must either:

    ...