Skip to main content
Telara

Integrations / OpenAI Admin API

OpenAI Admin API logo

OpenAI Admin API

OpenAI organization Admin API — Usage, Costs, and Audit Logs for per-project / per-user / per-key token spend governance.

API key
Spend
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

OpenAI Admin keys start with sk-admin- and are issued from the OpenAI platform under Settings → Admin keys (Organization Owner role required). A project key (sk-proj-...) cannot access org-level usage data. For project-level or personal API usage tracking, use the OpenAI Direct connector instead.
An OpenAI Organization you own or administer.
Organization Owner (or the Admin keys role OpenAI currently requires).

Vendor setup

Get the credential

1
Open Admin keys
In the OpenAI platform, open Settings → Admin keys. This is not the default project API keys page.
2
Create an organization admin key
Issue the organization admin key. Project keys are the wrong class and will be rejected.
3
Paste in Telara
Settings → Integrations → OpenAI Admin.

In Telara

Connect in Telara

API key

OpenAI Admin API key (prefix `sk-admin-...`). DIFFERENT from a standard project API key (`sk-proj-...`) or a user key (`sk-...`). Admin keys can ONLY be issued from the Organization owner role via the OpenAI platform UI (Settings → Admin keys); they are NOT mintable through the API itself. Auth header is Authorization: Bearer <key>. No additional version or beta header is required for the Usage / Costs / Audit Logs endpoints as of 2026-05. Per research §4: OpenAI's project-scoped keys + per-project user assignment is the cleanest BYO-key attribution model in market — project_id maps cleanly to a Telera team, project users map cleanly to humans. Customers should issue ONE project per team (or per cost-center) and assign humans to projects, NOT share one org-wide key.

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

Fields Telara asks for
  • Admin Api Key

Spend

What gets measured

Resolution: Not published.

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
  • input_tokens_cached
    tokens
  • output_tokens
    tokens
  • input_audio_tokens
    tokens
  • output_audio_tokens
    tokens
  • requests
    requests
  • cost_amount_usd
    usd

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

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

OpenAI Admin keys start with sk-admin- and are issued from the OpenAI platform under Settings → Admin keys (Organization Owner role required). A project key (sk-proj-...) cannot access org-level usage data. For project-level or personal API usage tracking, use the OpenAI Direct connector instead.

Honesty

Known limitations

Project keys and personal keys cannot read org-level usage. Use the OpenAI Direct connector for those.
The authorizing user must be an organization owner; a project member is not enough.