About OpenAI Admin
The OpenAI Admin integration connects Serval workflows to OpenAI’s organization-management API. The shipped workflows invite and remove users, change organization roles, list and revoke invites, create and archive projects, list Admin API keys, report costs, read audit logs, and set the organization spend limit. Custom workflows can also manage project members, groups and service accounts, revoke project keys, adjust project rate limits and model permissions, set spend alerts, and pull usage data. It’s built for the IT or platform team that owns the OpenAI organization: provisioning, off-boarding, key hygiene, and spend monitoring. This is separate from Serval’s OpenAI workflow actions, which generate text inside workflows. The Admin integration never calls a model. Authentication: OpenAI Admin API key. One key, created under the organization’s Admin keys settings, pasted into the connect form. Serval stores it securely and attaches it to every request; workflow code never sees the key. Standard project API keys can’t call administration endpoints, and Admin API keys can’t call inference endpoints. Data sync: On demand only. Serval calls OpenAI when a workflow runs. There is no background sync. What a workflow returns, such as a user list or audit events, stays in that run’s history and is visible to the people who can see the run.What the integration enables
Read-only workflows run without approval. Invitations, role changes, removals, project changes, and spend-limit changes default to installer approval when installed.
The typed action is generated from the official
openai/openai-openapi specification. See the OpenAI Administration API reference for every endpoint.
Get your credentials
This integration requires an OpenAI Admin API key, which only an organization owner can create. It’s a different credential from the project API keys used to call models.1
Sign in to the OpenAI Platform
Sign in at platform.openai.com as an organization owner.
2
Open the Admin keys page
Open Organization settings, then Admin keys.
3
Create an admin key
Select Create admin key and give it a descriptive name, for example Serval Production.
4
Copy the key immediately
OpenAI shows the secret once. Copy it right away and keep it in your secret manager until you connect the integration.
Connect in Serval
1
Open the OpenAI Admin integration
In Serval, open Integrations, select All integrations, choose OpenAI Admin, and start a new connection.
2
Paste your admin key
Paste the full key into the Admin API Key field. It’s a password field, so the value stays hidden as you type.
3
Submit the form
Select Submit. Serval verifies the key by listing one organization user.
Verifying the connection
When you submit the form, Serval verifies the key by listing one organization user. The integration also ships three health checks you can run from the connection page:
The most common cause of the first two failing is pasting a project API key instead of an admin key. The audit-log check also fails when nobody has turned on audit logging for the organization, even with a valid key.
Gotchas and troubleshooting
Admin and project keys aren't interchangeable
Admin and project keys aren't interchangeable
A project API key can’t manage the organization, and an Admin API key can’t call the Responses, Chat Completions, or other inference APIs. Use the OpenAI provider configuration for model calls and this integration for administration.
Admin keys are organization-wide credentials
Admin keys are organization-wide credentials
An Admin API key can remove users, archive projects, revoke other keys, and change spend and security settings across the whole organization. Treat it as the most sensitive credential in your stack, restrict who can connect or rotate it, and keep the approval defaults on destructive workflows.
Audit logs need to be turned on in OpenAI
Audit logs need to be turned on in OpenAI
OpenAI records organization audit events only after an organization owner turns on audit logging in the organization settings. Until then the List OpenAI Audit Logs health check fails and the audit-log workflow returns an error, even with a valid Admin API key.
Key creation isn't modeled, on purpose
Key creation isn't modeled, on purpose
Creating an Admin API key, a service account, or a service-account key returns a new secret. Those operations are excluded from the typed action, and Serval’s proxy refuses them even when a custom workflow builds the request by hand, so credentials can never land in workflow run history. Create keys in the OpenAI console and use Serval for inventory and revocation.
Certificate uploads aren't modeled
Certificate uploads aren't modeled
OpenAI’s certificate endpoints accept binary request bodies. Serval’s typed workflow action is JSON-only, so certificate upload, activation, and deactivation are excluded.
Filtering audit logs by time
Filtering audit logs by time
The audit-log endpoint takes an
effective_at object with gt, gte, lt, and lte members in Unix seconds, and array filters named with brackets such as project_ids[]. Pass them as the typed action expects. Serval sends every array as bracketed repeated keys, the shape OpenAI’s own SDKs use, and range objects as effective_at[gte]=....List endpoints are paginated
List endpoints are paginated
Most list responses return
has_more and a last_id cursor to pass as after. The costs and usage endpoints return next_page to pass as page instead. The shipped workflows page through every result for you.Organization and project roles
Organization and project roles
Organization roles are
owner and reader, and project roles are owner and member. The shipped Update OpenAI User Role workflow changes the organization role. To change a project role, send a custom request to the project users endpoint. Custom roles, and assigning or revoking them, go through the roles endpoints under /v1/organization/roles.Need help? Contact support@serval.com for assistance with your OpenAI Admin integration.

