Integrations / LiteLLM Proxy (Webhook)

LiteLLM Proxy (Webhook)

Push-based LiteLLM Proxy spend delivery: the proxy's success callback (litellm_settings.success_callback: ["webhook"] / generic HTTP callback) POSTs a top-level JSON ARRAY of StandardLoggingPayload rows directly, instead of Telara polling /spend/logs. Complements the `litellm` pull connector. LiteLLM has no HMAC signing for custom webhooks; the tenant provisions a shared secret via the ?token= query parameter instead. TENG-2189.

See connection fields

Spend

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI No Runs actions No Real-time events No

Before you connect

Prerequisites

Access to LiteLLM Proxy (Webhook) alert or webhook settings.

The webhook URL Telara shows after you open this connector.

Vendor setup

Get the credential

Copy the Telara webhook URL

Open Settings → Integrations, choose this connector, and copy the inbound URL Telara displays.

Add it in LiteLLM Proxy (Webhook)

In LiteLLM Proxy (Webhook), create an alert or webhook destination and paste that URL. Do not paste a vendor API key on this page.

In Telara

Connect in Telara

Spend

What gets measured

Resolution: Per request.

Attribution: Matched to people by the vendor user id.

How far back vendor history goes is not published uniformly for this connector.

input_tokens
tokens
output_tokens
tokens
requests
count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Events only arrive after the vendor fires an alert. A quiet project looks empty.

This page is the webhook path. The vendor’s API-key connector, if Telara has one, is separate.