Tollara icon

Tollara

Tollara marketplace operations: authenticate requests, invoke services, manage async jobs, and report usage

Actions9

Usage → Estimate Usage

AI-generated

Summary

Estimate usage cost, quota sufficiency, and related metadata for a Tollara service key by submitting an estimated number of usage units.

Inputs

  • Service Key (required) — The service key associated with the Tollara service, required for usage estimation.
  • Service Secret — Optional HMAC secret for the Tollara service; used for signing or verification, configured when multiple services are used in a workflow.
  • Service ID — UUID of your Tollara service from the Service Workspace, recommended for pinning validation to a specific service; if omitted, it is inferred from the service key.
  • Estimated Units (required) — The number of usage units to estimate; must be a positive number.
  • Set API Endpoints — Toggle to override the default Tollara core API URLs.
  • Validation API URL — When Set API Endpoints is enabled, specifies the URL used for validation and usage estimation API calls.

Output shape

a list of items, one per input, each with JSON containing estimation results or error details

Each output item includes a 'tollaraOk' boolean indicating success; on success, detailed fields such as sufficientCredits, wouldExceedCap, estimatedCost, billingModelType, measurementType, unitLabel, and usage breakdown are returned. On failure, error code and message fields are included. The operation performs secure HMAC validation of responses.

Links

Discussion