Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.requesty.ai/llms.txt

Use this file to discover all available pages before exploring further.

Requesty’s spending alerts let you monitor costs across your organization in real time. Define threshold rules for users, groups, or the organization as a whole, and receive instant notifications via webhook whenever a threshold is crossed.

​
How Alerts Work

Every time a request is processed, Requesty evaluates the updated spend against your configured alert thresholds. When a threshold is crossed for the first time, a notification is dispatched to your webhook endpoint. Alerts fire exactly once per threshold crossing — they will not repeat until the threshold is crossed again (e.g. in a new billing cycle).

​
Alert Types

Requesty supports six types of spending alerts, each designed for a different monitoring scenario:

User % of Budget

Triggers when a user’s monthly spend reaches a percentage of their configured budget. Applies to both global user budgets and group-based user budgets.

User Absolute Spend

Triggers when a user’s monthly spend reaches a specific dollar amount. Applies to both global user spend and group-based user spend. Works even if no budget limit is set.

Group % of Budget

Triggers when a group’s combined monthly spend reaches a percentage of the group’s budget.

Org Balance Below

Triggers when the organization’s remaining balance drops below a specific dollar amount — useful for ensuring you top up before running out of credits.

API Key % of Budget

Triggers when an API key’s monthly spend reaches a percentage of its configured monthly budget. Requires a monthly spend limit to be set on the API key.

API Key Absolute Spend

Triggers when an API key’s monthly spend reaches a specific dollar amount. Works even if no budget limit is set on the key.

​
Alert Type Examples

Alert TypeThreshold UnitExampleWhen It Fires
User % of BudgetPercentage (0–100%)80%User has spent 80% of their monthly limit
User Absolute SpendDollar amount$50User has spent $50 this month (globally or within a group)
Group % of BudgetPercentage (0–100%)90%Group has spent 90% of its monthly limit
Org Balance BelowDollar amount$100Organization balance drops below $100
API Key % of BudgetPercentage (0–100%)80%API key has spent 80% of its monthly limit
API Key Absolute SpendDollar amount$25API key has spent $25 this month
You can create multiple thresholds per alert type. For example, set User % of Budget alerts at both 50% and 80% to get an early warning and a critical warning.

​
Setting Up Alerts

​
Step 1: Configure a Webhook

Before alerts can be delivered, you need to configure a webhook endpoint for your organization.
  1. Go to the Admin Panel and navigate to the Alerts tab
  2. Click Add Webhook in the header
  3. Choose a webhook type:
    • JSON (Generic) — sends a structured JSON payload to any HTTP endpoint
    • Slack — sends a pre-formatted message to a Slack incoming webhook URL
    • Teams — sends a Microsoft Adaptive Card to a Teams incoming webhook URL
  4. Enter your webhook URL
  5. Click Save
Alerts will not be sent unless a valid webhook URL is configured. If you create alert thresholds without a webhook, they will be stored but no notifications will be delivered.

​
Step 2: Create Alert Thresholds

  1. In the Alerts tab, click Add Alert
  2. Select an alert type from the dropdown
  3. Enter the threshold value:
    • For percentage-based alerts, enter a number between 1 and 100
    • For dollar-based alerts, enter the dollar amount
  4. Click Create Alert
You can create as many thresholds as needed across all alert types.

​
Webhook Payload Formats

​
JSON Webhook

When the webhook type is set to JSON, alerts are delivered as a structured JSON payload via HTTP POST: 
{
  "type": "user.budget.exceeded_percent",
  "data": {
    "user_email": "[email protected]",
    "limit": "100",
    "percentage_exceeded": "0.8"
  }
}

​
Slack Webhook

When the webhook type is set to Slack, alerts are delivered as Slack-formatted messages. Each alert type produces a human-readable notification:
  • User % of budget alerts: “User Spend Threshold Exceeded — [email protected] exceeded 80% of their $100 monthly limit” (includes group name when triggered within a group)
  • User absolute spend alerts: “User Spend Threshold Exceeded — [email protected] exceeded $50 spend threshold” (includes group name when triggered within a group)
  • Group alerts: “Group Spend Threshold Exceeded — Engineering exceeded 90% of the $500 monthly limit” (includes group admin emails)
  • Org alerts: “Organization Balance Alert — Organization balance has dropped below $100 threshold. Current balance: 87.50”
  • API key % of budget alerts: “API Key Spend Threshold Exceeded — API key production-key exceeded 80% of the $100 monthly limit”
  • API key absolute spend alerts: “API Key Spend Threshold Exceeded — API key production-key exceeded $50 spend threshold”

​
Teams Webhook

When the webhook type is set to Teams, alerts are delivered as Adaptive Card messages via HTTP POST. Each alert is rendered as a card with a bold title and a descriptive body inside Microsoft Teams. The payload follows the Teams incoming webhook Adaptive Card format:
Example Adaptive Card Payload
{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "type": "AdaptiveCard",
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "version": "1.4",
        "body": [
          {
            "type": "TextBlock",
            "text": "⚠ User Spend Threshold Exceeded",
            "weight": "Bolder",
            "size": "Medium"
          },
          {
            "type": "TextBlock",
            "text": "**[email protected]** exceeded **80%** of their **$100** monthly limit in group **Engineering**",
            "wrap": true
          }
        ]
      }
    }
  ]
}
Each alert type produces the following card titles and body text:
Alert TypeTitleBody
User % of budget⚠ User Spend Threshold Exceeded[email protected] exceeded 80% of their $100 monthly limit (includes group name when triggered within a group)
User absolute spend⚠ User Spend Threshold Exceeded[email protected] exceeded $50 spend threshold (includes group name when triggered within a group)
Group⚠ Group Spend Threshold ExceededEngineering exceeded 90% of the $500 monthly limit (includes group admin emails)
Org⚠ Organization Balance AlertOrganization balance has dropped below 100∗∗threshold.Currentbalance:∗∗100** threshold. Current balance: **87.50
API key % of budget⚠ API Key Spend Threshold ExceededAPI key production-key exceeded 80% of the $100 monthly limit
API key absolute spend⚠ API Key Spend Threshold ExceededAPI key production-key exceeded $50 spend threshold
To set up a Teams incoming webhook, create one via the Workflows app in Microsoft Teams (or the legacy “Incoming Webhook” connector). Copy the generated URL and paste it into the Requesty webhook configuration.

​
Webhook Delivery

Requesty’s webhook dispatcher ensures reliable delivery:
  • Retries: Failed deliveries are retried up to 3 times with exponential backoff
  • Timeout: Each delivery attempt times out after 15 seconds

​
Managing Alerts

​
Viewing Active Alerts

All configured alert thresholds are visible in the Alerts tab of the Admin Panel. The table shows:
  • Alert type and description
  • Threshold value
  • Status (active)

​
Deleting Alerts

To remove an alert threshold, click the delete icon next to the alert in the table and confirm the deletion.

​
Updating the Webhook

Click Edit next to the webhook display in the Alerts header to change the webhook type or URL. Updating the webhook takes effect immediately for all future alert notifications.

​
Example Configurations

  • Org Balance Below $50 — get notified before credits run out
  • User Absolute Spend $20 — catch unexpectedly high individual usage
  • Webhook: Slack channel #billing-alerts
  • User % of Budget at 50%, 80%, 95% — progressive warnings as users approach limits
  • Group % of Budget at 80%, 95% — monitor departmental spend
  • Org Balance Below 500,500, 200 — early and critical low-balance warnings
  • User Absolute Spend 100,100, 500 — catch runaway usage regardless of budget
  • Webhook: JSON endpoint integrated with internal alerting system (e.g., PagerDuty, Opsgenie)
  • API Key % of Budget at 50%, 80%, 95% — progressive warnings as keys approach their limits
  • API Key Absolute Spend 25,25, 50 — track per-key usage by dollar amount
  • Org Balance Below $100 — ensure account stays funded
  • Webhook: JSON endpoint for automated processing

Spend Limits

Set hard spending caps at the user, project, or API key level to enforce budgets automatically.

Groups

Organize users into groups with shared budgets and collective spending tracking.

Usage Analytics

View detailed spending breakdowns and usage trends across your organization.

Cost Tracking

Monitor real-time costs per request, model, and user.
Last modified on May 11, 2026