MsgCore icon

MsgCore

Universal messaging gateway - send messages across multiple platforms

Billing → Usage

AI-generated

Summary

Get usage statistics for projects, messages, platforms, webhooks with limit warnings

Inputs

  • requestOptions — Optional configuration for the HTTP request execution. All sub-properties are optional and passed directly to the request context.
  • batching — Fixed collection to throttle requests by splitting input into batches. Controls batch size and interval between batches.
  • batchSize — Number of items per batch. -1 disables batching; 0 is treated as 1. Default: 50.
  • batchInterval — Time in milliseconds between each batch of requests. 0 disables interval. Default: 1000.
  • allowUnauthorizedCerts — Accept response even if SSL certificate validation fails. Default: false.
  • proxy — HTTP proxy URL (e.g., http://myproxy:3128). Supports embedded auth: http://username:password@myproxy:3128. Default: empty string.
  • timeout — Timeout in milliseconds for waiting on response headers. Minimum 1. Default: 10000.

Output shape

Usage statistics aggregated across projects, messages, platforms, and webhooks, including any server-side limit warnings.

The operation issues a GET request to /api/v1/billing/usage. Request options such as batching, proxy, SSL tolerance, and timeout are applied via the request configuration. No additional input parameters are required beyond requestOptions.

Examples

Example 1: Fetch basic usage stats with default settings.

Leave requestOptions at default {}. The node executes GET /api/v1/billing/usage with no extra parameters.

Example 2: Throttle requests to 20 items per batch with a 500ms interval.

Set requestOptions.batching.batch to { batchSize: 20, batchInterval: 500 }. All other options remain default.

Discussion