Zorus icon

Zorus

Interact with Zorus API

Actions13

Overview

The node interacts with the Zorus API to retrieve unblock requests. Specifically, the "Unblock Request" resource with the "Unblock Request" operation allows users to query unblock request records based on various filtering and sorting criteria. This is useful in scenarios where an organization needs to monitor or manage unblock requests submitted by customers or users, for example, to audit access requests or automate follow-up actions.

Practical examples include:

  • Fetching all unblock requests made by a specific customer within a date range.
  • Retrieving unblock requests sorted by creation date to process the most recent ones first.
  • Filtering unblock requests related to a particular policy or user.

Properties

Name Meaning
Page The page number of results to retrieve (pagination).
Page Size Number of unblock request items to retrieve per page.
Sort Property The property by which to sort the results (e.g., createdAt).
Sort Ascending Whether to sort the results in ascending order (true) or descending order (false).
Customer UUID In Filter unblock requests by the UUID of the customer who made the request.
Policy UUID In Filter unblock requests by the UUID of the associated policy.
Logged On User Contains Filter unblock requests where the logged-on user's name contains this string.
Requested Before Filter unblock requests made before this date (ISO 8601 string expected).
Requested After Filter unblock requests made after this date (ISO 8601 string expected).

Output

The node outputs JSON data representing the list of unblock requests matching the specified filters and pagination. Each item typically includes details such as identifiers, timestamps, customer and policy references, and user information related to the unblock request.

If the node supports binary data output, it would represent any file attachments or related binary content associated with unblock requests; however, based on the provided code and properties, the primary output is structured JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Zorus API.
  • The node configuration must include this API key credential.
  • Network access to https://developer.zorustech.com/api is necessary.

Troubleshooting

  • Common issues:
    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect date formats in "Requested Before" or "Requested After" may result in errors or no data returned.
    • Pagination parameters out of range might return empty results.
  • Error messages:
    • Authentication errors indicate problems with the API key; verify the credential setup.
    • Validation errors on input properties suggest checking the format and values of filters.
    • Network errors imply connectivity issues to the Zorus API endpoint.

Links and References

Discussion