OpenAI (Usage & Costs API)
Business software
Sync OpenAI organization usage and cost data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.
The OpenAI connector syncs your organization's API usage and billing data into analytics-ready tables in your data warehouse. Pull usage and cost records from OpenAI's Usage and Costs API, with Ingest handling auth, pagination, and retries so the tables stay current. This is a distinct, Admin-key-gated reporting surface — separate from the completions/chat API most developers use.
What you would get
Each of these arrives as its own table, kept current on the schedule you choose:
- Usage
- Costs
How it gets built
- Choose OpenAI (Usage & Costs API) when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads OpenAI (Usage & Costs API)'s documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against OpenAI (Usage & Costs API) itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
Admin API key (Bearer token). An Organization Owner creates an Admin API key at platform.openai.com/settings/organization/admin-keys; regular project API keys can't call these endpoints.
You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.
Questions
- Does Ingest have a OpenAI (Usage & Costs API) connector?
- Not as a finished connector yet. Ingest builds it from OpenAI (Usage & Costs API)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can OpenAI (Usage & Costs API) data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
OpenAI (Usage & Costs API) API documentation: https://developers.openai.com/cookbook/examples/completions_usage_api
Where this would land, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.