Integrations / Replit Enterprise

Replit Enterprise

Replit Enterprise — engagement and spend analytics exist in the admin dashboard with SCIM provisioning. apis.io lists Deployments / Repls / Users management APIs only (no usage, credits, or spend export). Catalogued as coming_soon until Replit ships a pull surface; prefer routing model traffic through an LLM gateway (OpenRouter / LiteLLM / Portkey) for attributable spend today.

API key

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Replit Enterprise organization. Personal Replit does not expose an admin usage API yet.

Org admin. Do not paste a personal Replit login token into Telara.

Vendor setup

Get the credential

Open organization settings

Sign in to Replit as an Enterprise admin. Open the organization → Settings → API (or Admin → API keys) if that page exists on your contract.

Create an admin key only when Replit shows one

If Replit has enabled an admin/usage API for your org, create a key, copy it once, and note any org id on that page. If the page is missing, stop — this connector is reserved until that API ships; do not paste a session cookie.

Paste in Telara

Settings → Integrations → Replit Enterprise. Paste only what the Connect form asks for. If Connect is marked coming soon, wait — a personal token will not become an admin API.

In Telara

Connect in Telara

API key

Reserved for a future Replit admin/usage API. Do not collect keys in Connect until spend_connector ships (coming_soon on the billing catalog).

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API key

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

This connector is reserved until Replit’s admin usage API ships. A green Connect with a personal token is the wrong credential.

Teams and Enterprise are different. Only Enterprise is in scope here.