Disglow icon

Disglow

Interact with Disglow API

Actions7

Overview

This node interacts with the Disglow API, specifically providing functionality to retrieve API usage logs when using the Logs resource with the Get API Logs operation. It allows users to fetch detailed records of API requests made, which can be filtered and paginated. This is useful for monitoring API activity, debugging issues, auditing usage patterns, or analyzing performance.

Practical examples include:

  • Retrieving the last 50 API calls to check recent activity.
  • Filtering logs to see only POST requests to a specific endpoint.
  • Paginating through logs by skipping a number of entries.
  • Filtering logs by HTTP status codes to identify errors or successful calls.

Properties

Name Meaning
Limit Number of logs to retrieve (maximum 100).
Offset Number of logs to skip for pagination purposes.
Method Filter Filter logs by HTTP method. Options: All (no filter), GET, POST, DELETE.
Endpoint Filter Filter logs by endpoint URL path (partial match).
Status Filter Filter logs by HTTP status code (e.g., 200, 404).

Output

The node outputs an array of JSON objects representing the API logs retrieved from Disglow. Each log entry contains details about individual API requests such as method, endpoint, status code, timestamp, and possibly other metadata provided by the Disglow API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Disglow API.
  • The node makes HTTP requests to https://api.disglow.app/api/v1.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Exceeding the maximum limit of 100 logs per request may cause errors; ensure the "Limit" property does not exceed 100.
    • Incorrect or missing API credentials will result in authentication failures.
    • Providing invalid filter values (e.g., non-numeric status code) might cause the API to reject the request.

  • Error Messages:

    • "The operation "getLogs" is not known!" — This indicates an internal error where the operation was not recognized; verify that the node is configured correctly.
    • Authentication errors typically indicate invalid or missing API keys; recheck credential setup.
    • HTTP errors returned from the API (e.g., 400 Bad Request) usually relate to invalid parameters; review filter inputs.

Links and References

Discussion