Which OpenAI API key does the connector need?

An organization **Admin API key** that starts with sk-admin. You can create one at platform.openai.com under **Organization settings** > **Admin keys**. Regular project API keys are rejected by the Admin API reporting endpoints, so they will not work.

Do I need a separate connection for each OpenAI project?

No. The Admin API key is organization-scoped, so one connection covers every project in your organization. Use the Project ID column (and Project Name in the cost report) to separate projects in the destination table.

What is the difference between usage reports and the cost report?

Usage reports measure volumes: tokens, images, audio seconds, characters, storage bytes, sessions, and request counts per API capability, with minute, hour, or day buckets. The cost report measures money: daily amounts in USD broken down by project, user, API key, and line item.

Why are the User ID or API Key ID columns empty in some rows?

The OpenAI API returns null for a dimension when the usage cannot be attributed to a specific user, key, or project. Such rows still carry the correct totals; only the attribution is missing.

OpenAI

The OpenAI Admin API exposes two kinds of organization-wide reporting: usage reports, one per API capability, and a daily cost report with amounts in USD. Usage reports cover completions, embeddings, images, audio, moderations, vector stores, and code interpreter sessions.

Renta syncs both to your data warehouse as time-bucketed statistics broken down by project, user, API key, and model.

Authentication

Renta authenticates with an organization Admin API key. Create one at platform.openai.com under Organization settings > Admin keys: the key starts with sk-admin. Regular project API keys are rejected by the Admin API reporting endpoints.

When you save the connection, Renta validates the key against the OpenAI Admin API, so an invalid or non-admin key returns an error immediately instead of failing on the first pipeline run.

Connect OpenAI source

Follow these steps to add OpenAI as a source in Renta using an Admin API key.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the AI category and click the OpenAI card.

OpenAI card in the AI category of the Renta catalog

Enter the Admin API key and saveStep 2

Fill in the connection form:

Source name.
Specify a name for this data source. This is used exclusively in the Renta interface.
Admin API key.
Paste your OpenAI Admin API key (starts with sk-admin).

Click Save to finish.

Add a new OpenAI connection page with source name and Admin API key fields

Source createdStep 3

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Create a pipeline

Once the source is connected, create a pipeline to sync your OpenAI data into your destination.

Create an OpenAI pipeline

Link your OpenAI source to a destination and configure the pipeline.

Select OpenAI as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select OpenAI under Already connected and click Next step.

Select a source step with OpenAI under Already connected

Select your OpenAI connectionStep 2

Choose the OpenAI connection you created earlier and click Next step.

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose which OpenAI report to export and how Renta loads it.

Report type and granularity

Pick the report and the size of its time buckets.

Report Types Choose one of the nine reports. Each pipeline exports one report into one destination table.

Report type	Data
Completions Usage	Input and output token counts for completions, including cached, text, audio, and image token breakdowns, plus request counts.
Embeddings Usage	Input token counts and request counts for embeddings.
Images Usage	Number of generated images and request counts, with image size and source breakdowns.
Audio Speeches Usage	Characters processed by text-to-speech and request counts.
Audio Transcriptions Usage	Seconds of transcribed audio and request counts.
Moderations Usage	Input token counts and request counts for moderations.
Vector Stores Usage	Vector store storage usage in bytes.
Code Interpreter Sessions Usage	Number of code interpreter sessions.
Cost Report	Daily costs in USD broken down by project, user, API key, and line item.

Granularity Choose the time bucket size: Minute, Hour, or Day. Each row in the destination table is one time bucket for one combination of breakdown values. For Cost Report the only option is Day: the OpenAI costs endpoint supports daily buckets only.

A day contains 1,440 minute buckets, so Minute granularity over a long date range produces a large table and a noticeably longer initial load. For historical analysis, Day is usually enough.

Parameters

Select the fields to include in the destination table. The available set depends on the report type: each report combines breakdown columns, its own metrics, and time bucket fields.

Check the fields in the picker or click Select All. The Selected tab shows everything you picked, and the Selected Parameters list below lets you remove a field. In the destination table, column names use the API names shown under each field: Project ID becomes project_id.

Report type	Breakdowns	Metrics
Completions Usage	Project ID, User ID, API Key ID, Model, Batch, Service Tier	Input Tokens (with cached, uncached, cache write, text, audio, and image variants), Output Tokens (with text, audio, and image variants), Model Requests
Embeddings Usage	Project ID, User ID, API Key ID, Model	Input Tokens, Model Requests
Images Usage	Project ID, User ID, API Key ID, Model, Size, Source	Images, Model Requests
Audio Speeches Usage	Project ID, User ID, API Key ID, Model	Characters, Model Requests
Audio Transcriptions Usage	Project ID, User ID, API Key ID, Model	Seconds, Model Requests
Moderations Usage	Project ID, User ID, API Key ID, Model	Input Tokens, Model Requests
Vector Stores Usage	Project ID	Usage Bytes
Code Interpreter Sessions Usage	Project ID, API Key ID	Sessions
Cost Report	Project ID, Project Name, Organization ID, Organization Name, User ID, User Email, API Key ID, Line Item	Amount Value, Amount Currency, Quantity

Every report also includes three time fields: Bucket Starting At and Bucket Ending At (bucket boundaries in UTC) and Bucket Starting Date, the day-level date column the destination table is partitioned by. Bucket Starting Date is pre-selected and cannot be removed.

Breakdown columns can be null: the OpenAI API omits the attribution when usage cannot be tied to a specific project, user, or API key. The totals in such rows are still correct.

Table name and date range

Name the pipeline and set the historical period to load.

OpenAI integration name and table name fields

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

OpenAI date range with date start and date end fields

Date start.
The first date of the extraction period.
Date end.
The last date of the extraction period. Leave it as Today to keep collecting new data on every run.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run.

On each run, Renta re-fetches the report starting from the date of the last successful run minus the overwrite period. The affected days are deleted from the destination table and inserted again, while older data stays untouched. The default is Last 1 day.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new OpenAI integration

Sync strategy

All OpenAI reports are time-bucketed statistics, so they share one synchronization strategy.

Strategy	Supported report types	Description
Incremental	Completions Usage, Embeddings Usage, Images Usage, Audio Speeches Usage, Audio Transcriptions Usage, Moderations Usage, Vector Stores Usage, Code Interpreter Sessions Usage, Cost Report	Each destination table is partitioned by the `bucket_starting_date` column. On every run Renta reloads the window from the last successful run minus the overwrite period to the end of the date range: those daily partitions are deleted and inserted again, and older partitions stay untouched.

Changing the selected parameters updates the table schema, so the next run after the change reloads the entire date range.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.