Dovkie
Sign in
Back to monitors

openai

OpenAI API

REST
OpenAPI (YAML)
https://app.stainless.com/api/spec/documented/openai/openapi.documented.yml
Informational AI classification

SDK code examples updated for Admin API method naming

SDK code examples in the OpenAPI specification were updated to reflect the corrected naming conventions for creating service account API keys. The examples now show apiKeys.create() (and language-specific equivalents) instead of createAPIKey(), and response variable names were changed from response to apiKey for clarity. These are documentation changes to example code only—the actual API endpoint paths and request/response schemas remain unchanged.

Alert history

  • Informational

    SDK code examples updated for Admin API method naming

    SDK code examples in the OpenAPI specification were updated to reflect the corrected naming conventions for creating service account API keys. The examples now show apiKeys.create() (and language-specific equivalents) instead of createAPIKey(), and response variable names were changed from response to apiKey for clarity. These are documentation changes to example code only—the actual API endpoint paths and request/response schemas remain unchanged.

  • Informational

    Refactor batch and service account schemas to reusable components

    The diff reorganizes OpenAPI schema definitions by extracting inline object schemas into reusable component schemas: CreateBatchRequest, BatchError, BatchRequestCounts, CreateProjectServiceAccountApiKeyBody, and ServiceAccountApiKeyBody. Request/response payloads now reference these components via $ref instead of defining them inline. This is a documentation-only restructuring that does not alter the actual API behavior, request formats, or response structures.

  • Additive

    Add service account API key creation endpoint and usage token fields

    This release adds a new POST endpoint /organization/projects/{project_id}/service_accounts/{service_account_id}/api_keys for creating API keys under service accounts, along with a new optional create_service_account_only parameter for service account creation. It also expands usage reporting fields to distinguish between text, audio, and image tokens (adding input_cached_text_tokens, output_text_tokens, input_cached_audio_tokens, input_image_tokens, input_cached_image_tokens, output_image_tokens, and others), adds numerous new webhook event types for tenant management, and updates response schema structure for annotations. All changes are backward-compatible.

  • Additive

    Add owner_project_access to project API keys

    The project API keys endpoint now includes an optional owner_project_access query parameter and returns an owner_project_access field in responses. This allows filtering and visibility of whether API key owners have effective access to the project. The WebhookSafetyIdentifierBlocked webhook type has been removed from the API specification.

  • Additive

    Add Responses beta API and new WebSocket support

    Added a new /responses?beta=true endpoint for beta Responses API functionality, including new request/response schemas (BetaCreateResponse, BetaResponse), model updates (e.g., gpt-5.4 → gpt-5.6-sol in examples), and documentation for WebSocket client/server events and new webhook event type WebhookSafetyIdentifierBlocked. Also added optional detail field to input file requests. These changes are purely additive and do not break existing integrations.

  • Additive

    Add tunnel_id option for MCP server configuration

    A new optional field tunnel_id has been added to MCP server configuration, allowing secure tunnel connections as an alternative to server_url or connector_id. Documentation has been updated across multiple fields to reflect that one of three options (server_url, connector_id, or tunnel_id) is now required instead of two. Additional clarifications were added to video generation parameters to document reference format requirements.

  • Additive

    Add SDK code examples for spend alert endpoints

    Added code examples in Node.js, Python, Go, Java, and Ruby for two spend alert retrieval endpoints: retrieving project-level and organization-level spend alerts. These are documentation-only additions that do not change the API contract itself, and include a minor schema reference fix changing Reasoning-2 to Reasoning plus documentation cleanup of redundant field descriptions.

  • Additive

    Multiple additive API improvements for keys, alerts, and reasoning

    This release adds several new features: API key expiration support (expires_at response field and expires_in_seconds request parameter), two new GET endpoints for retrieving project and organization spend alerts, a new tenant_only query parameter for audit logs, new context parameter for reasoning configuration, and new Reasoning-2 schema for response-level reasoning metadata. Additionally, it clarifies documentation for video generation parameters and deprecates the truncation field in the ReasoningConfiguration schema in favour of the Response schema. All changes are additive or documentation clarifications with no breaking removals.

  • Additive

    Add moderation support to chat and response completions

    New optional moderation parameter and response fields added to the chat completions and response completions endpoints. The changes enable clients to optionally request moderation results for request input and generated output by passing a ModerationParam configuration. When enabled, responses include ChatCompletionModeration or Moderation objects containing moderation results or errors.

  • Additive

    New workload identity provider event types and AdditionalTools schema

    The diff adds new event types for workload identity provider management (workload_identity_provider.created, workload_identity_provider.updated, workload_identity_provider.deleted, and their mapping variants) and introduces a new AdditionalTools schema for specifying additional tool definitions. It also adds a personality parameter to requests, clarifies prompt_cache_retention documentation for new models, and marks the query field as deprecated in favor of queries (though the field remains supported). These are purely additive changes that expand API capabilities without breaking existing integrations.

  • Additive

    Add data retention and spend alert endpoints and schemas

    The diff adds two new REST endpoints for organization and project data retention management (GET/POST /organization/data_retention), new spend alert functionality for projects, and supporting request/response schemas. It also adds assignment_sources field to user project responses and enumerations for group types. These are purely additive changes that extend the API without breaking existing integrations.

  • Informational

    Clarify open_page action type description

    Updated the description of the type field in the open_page action to clarify that it is always set to open_page. This is a documentation improvement that does not change the API contract or behaviour.

  • Informational

    Add SDK code examples for admin APIs

    Added code examples in Node.js, Python, Go, Java, and Ruby for several admin API endpoints covering hosted tool permissions, model permissions, and usage metrics. These are documentation-only additions that do not change API behavior or endpoints.

  • Additive

    Add hosted tool and model permissions endpoints and usage endpoints

    Added new endpoints for managing project-level hosted tool permissions (/organization/projects/{project_id}/hosted_tool_permissions) and model permissions (/organization/projects/{project_id}/model_permissions), along with new usage result schemas (UsageFileSearchCallsResult and UsageWebSearchCallsResult) and a new CompactionTriggerItemParam schema. All changes are purely additive with no modifications to existing endpoints or schemas.