Disglow icon

Disglow

Interact with Disglow API

Actions7

Overview

This node interacts with the Disglow API to retrieve various types of data related to Discord servers, users, logs, and statistics. Specifically, for the Stats resource with the Get API Stats operation, it fetches usage statistics of the Disglow API over a specified number of days.

This node is beneficial when you want to monitor or analyze your API usage patterns, such as tracking request volumes or performance metrics over time. For example, you could use it to generate reports on how many API calls were made in the last month or to identify trends in API consumption.

Properties

Name Meaning
Period (days) Number of days for which to retrieve API usage statistics. Default is 30 days.

Output

The output JSON contains the API usage statistics data returned by the Disglow API for the requested period. The exact structure depends on the API response but typically includes aggregated metrics such as counts of requests, errors, or other relevant statistics over the specified timeframe.

No binary data is output by this operation.

Example output snippet (structure may vary):

{
  "totalRequests": 1234,
  "successfulRequests": 1200,
  "failedRequests": 34,
  "period": 30,
  "details": [
    {
      "date": "2024-05-01",
      "requests": 40,
      "errors": 2
    },
    ...
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the Disglow API.
  • The node makes HTTP requests to https://api.disglow.app/api/v1.
  • No additional environment variables are needed beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Requesting stats for an invalid number of days (e.g., negative or zero) might result in API errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "The operation \"getStats\" is not known!" — This indicates the operation parameter was incorrect or unsupported; ensure the operation is set to "Get API Stats".
    • HTTP error responses from the API (e.g., 401 Unauthorized) usually mean authentication issues; verify your API key credentials.
    • Timeout or network errors suggest connectivity issues; check your internet connection and API endpoint accessibility.

  • To handle errors gracefully, enable the node's "Continue On Fail" option if you want the workflow to proceed despite individual request failures.

Links and References

Discussion