h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

This node allows administrators to list all existing API keys in the system. It is useful for managing and auditing API keys, such as reviewing which keys are active, filtering keys by username, or paginating through large numbers of keys. For example, an admin can retrieve a list of API keys with pagination and filter them to find keys associated with a specific user.

Properties

Name Meaning
Additional Options Collection of optional parameters:
- Offset Number of API keys to skip before returning results (for pagination).
- Limit Maximum number of API keys to return (minimum 1).
- Filter Filter string to only return keys for usernames matching this filter.

Output

The node outputs JSON data containing the list of API keys retrieved from the server. The structure typically includes details about each API key such as its ID, associated username, creation date, expiration, and status. No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication to the H2O GPT API.
  • The base URL for API requests is derived from the provided credentials.
  • The node sends HTTP GET requests to the /admin/api_keys endpoint with query parameters for pagination and filtering.

Troubleshooting

  • Common issues:
    • Authentication errors if the API key credential is missing or invalid.
    • Permission errors if the authenticated user is not an administrator.
    • Invalid parameter values for offset or limit may cause request failures.
  • Error messages:
    • Unauthorized or forbidden errors indicate insufficient permissions.
    • Validation errors may occur if offset or limit are out of acceptable ranges.
  • Resolutions:
    • Ensure valid API key credentials with admin privileges are configured.
    • Verify that offset and limit values are within allowed bounds.
    • Check network connectivity and correct base URL configuration.

Links and References

Discussion