Appearance
Gemini 2.5 Flash (openai)
OpenAPI Specification
yaml
openapi: 3.0.1
info:
title: ''
description: ''
version: 1.0.0
paths:
/gemini-2.5-flash/v1/chat/completions:
post:
summary: Gemini 2.5 Flash (openai)
deprecated: false
description: >-
### Streaming Support
When `stream: true` is set in the request, the API returns responses as
server-sent events (SSE) with `Content-Type: text/event-stream`. This
allows for progressive response delivery, where message deltas are sent
incrementally as they are generated. Each event contains partial message
content, enabling real-time display of responses in your application.
**Streaming Response Format:**
- Content-Type: `text/event-stream`
- Each event line starts with `data: ` followed by JSON
- Events contain incremental message deltas
- Final event indicates completion with `finish_reason`
**Multimodal**
Supports text and image inputs
**Real-time Search**
Google Search grounding enabled
**Streaming**
Server-sent events support
**Flexible Roles**
Multiple message roles supported
<div style="padding: 20px; background-color: rgba(255, 152, 0, 0.05);
border: 1px solid rgba(255, 152, 0, 0.15); border-left: 6px solid
#ff9800; border-radius: 10px; margin: 25px 0;">
<div style="display: flex; align-items: center; margin-bottom: 12px;">
<span style="font-size: 22px; margin-right: 10px;">⚠️</span>
<strong style="color: #e65100; font-size: 17px;">Important: Unified Media Structure</strong>
</div>
<p style="color: #444; margin-bottom: 15px; line-height: 1.6; font-size: 14px;">
To simplify integration, <b>all media types</b> (Images, Videos, Audio, or Documents) in the <code>messages</code> array share the <b>exact same JSON structure</b>:
</p>
<ul style="color: #555; line-height: 1.8; margin-bottom: 15px; font-size: 14px;">
<li>The <code>type</code> field is <b>fixed</b> as <code>"image_url"</code></li>
<li>The <code>image_url</code> key name <b>remains unchanged</b> for all file types</li>
<li>Only the <code>url</code> value points to your specific media file</li>
</ul>
<div style="background-color: #fdfdfd; padding: 12px; border-radius: 6px; border: 1px solid #eee; font-family: 'SFMono-Regular', Consolas, monospace; font-size: 13px; color: #d32f2f;">
<span style="color: #888; font-style: italic;">// Example for Video/Audio/PDF/Image:</span><br>
{ "type": "image_url", "image_url": { "url": "https://..." } }
</div>
</div>
## Tools Parameter
The `tools` parameter is an optional array that allows you to define
functions the model can call. The array can contain multiple objects.
When using function calling, you can define multiple functions in the
array.
<div style="padding: 20px; background-color: rgba(255, 152, 0, 0.05);
border: 1px solid rgba(255, 152, 0, 0.15); border-left: 6px solid
#ffa000; border-radius: 12px; margin: 25px 0;">
<div style="display: flex; align-items: center; margin-bottom: 12px;">
<div style="background-color: #ffa000; color: #fff; padding: 4px 10px; border-radius: 6px; font-size: 12px; font-weight: 800; margin-right: 12px; letter-spacing: 1px;">RESTRICTION</div>
<strong style="color: #e65100; font-size: 16px;">Conflict Warning</strong>
</div>
<p style="color: #444; margin-bottom: 12px; line-height: 1.6; font-size: 14px;">
<b>Google Search</b> and <b>Function Calling</b> are <span style="color: #d32f2f; font-weight: bold; background: rgba(211, 47, 47, 0.05); padding: 2px 4px; border-radius: 4px;">mutually exclusive</span>.
</p>
<div style="display: flex; align-items: center; justify-content: center; background: rgba(255,255,255,0.5); padding: 10px; border-radius: 8px; border: 1px dashed #ffa000; margin-top: 10px;">
<div style="text-align: center; flex: 1;">
<code style="color: #ffa000; font-weight: bold;">Google Search</code>
</div>
<div style="color: #999; font-weight: bold; padding: 0 15px;">XOR</div>
<div style="text-align: center; flex: 1;">
<code style="color: #ffa000; font-weight: bold;">Function Calling</code>
</div>
</div>
<p style="color: #666; font-size: 13px; margin-top: 15px; font-style: italic;">
* You cannot use both features in the same request. Please choose the one that best suits your needs.
</p>
</div>
Use this format to enable Google Search grounding:
```json
{
"type": "function",
"function": {
"name": "googleSearch"
}
} This enables real-time information retrieval via Google Search.
Define your own functions with parameters. You can define multiple
functions in the `tools` array:
json
[
{
"type": "function",
"function": {
"name": "get_current_weather",
"description": "Get the current weather in a given location",
"parameters": {
"type": "object",
"properties": {
"location": {
"type": "string",
"description": "The city and state, e.g. San Francisco, CA"
},
"unit": {
"type": "string",
"enum": ["celsius", "fahrenheit"]
}
},
"required": ["location"]
}
}
},
{
"type": "function",
"function": {
"name": "get_stock_price",
"description": "Get the current stock price for a given symbol",
"parameters": {
"type": "object",
"properties": {
"symbol": {
"type": "string",
"description": "The stock symbol, e.g. AAPL"
}
},
"required": ["symbol"]
}
}
}
] ### Function Declaration Requirements
When implementing function calling in your prompt, you need to create a
`tools` array containing one or more function declarations. You can
define functions using JSON (specifically, a selected subset of OpenAPI
schema format).
A single function declaration can include the following parameters:
- **`name`** (string, required): The unique name of the function (e.g.,
`get_weather_forecast`, `send_email`). Use descriptive names without
spaces or special characters (use underscores or camelCase).
- **`description`** (string, optional but recommended): A clear and
detailed description of what the function does and its purpose. This is
crucial for the model to understand when to use the function. Be
specific and provide examples when necessary (e.g., "Find movie theaters
by location, with an option to also find movies currently showing at
those theaters.").
- **`parameters`** (object, required): Defines the input parameters
expected by the function. Contains:
- **`type`** (string): Specifies the overall data type, must be `"object"`.
- **`properties`** (object): Lists individual parameters, each with:
- **`type`** (string): The parameter's data type, such as `string`, `integer`, `boolean`, `array`.
- **`description`** (string): Description of the parameter's purpose and format. Provide examples and constraints (e.g., "City and state, e.g. 'San Francisco, CA' or a postal code like '95616'.").
- **`enum`** (array, optional): If parameter values come from a fixed set, use `enum` to list allowed values rather than just describing them in the description. This helps improve accuracy (e.g., `"enum": ["daylight", "cool", "warm"]`).
- **`required`** (array): An array of strings listing the parameter names required for the function to run.
## Response Format Parameter
The `response_format` parameter is an optional JSON Schema object that
defines the structure of the response. When provided, the model will
generate responses that conform to this schema.
<div style="padding: 20px; background-color: rgba(255, 87, 34, 0.03);
border: 1px solid rgba(255, 87, 34, 0.15); border-left: 6px solid
#ff5722; border-radius: 12px; margin: 25px 0;">
<div style="display: flex; align-items: center; margin-bottom: 15px;">
<div style="background-color: #ff5722; color: #fff; padding: 3px 10px; border-radius: 5px; font-size: 11px; font-weight: 800; margin-right: 12px; letter-spacing: 1px;">PARAMETER CONFLICT</div>
<strong style="color: #bf360c; font-size: 16px;">Incompatible Configuration</strong>
</div>
<p style="color: #444; margin-bottom: 15px; line-height: 1.6; font-size: 14px;">
The <code>response_format</code> parameter and <b>Function Calling</b> (tools) are <span style="color: #d84315; font-weight: bold; text-decoration: underline;">mutually exclusive</span>.
</p>
<div style="display: flex; align-items: stretch; background: #fff; border-radius: 8px; border: 1px solid #eee; overflow: hidden; margin: 10px 0;">
<div style="flex: 1; padding: 12px; text-align: center; background: rgba(0,0,0,0.02);">
<code style="color: #ff5722; font-size: 13px;">response_format</code>
</div>
<div style="display: flex; align-items: center; background: #ff5722; color: #fff; padding: 0 15px; font-size: 12px; font-weight: bold;">
OR
</div>
<div style="flex: 1; padding: 12px; text-align: center; background: rgba(0,0,0,0.02);">
<code style="color: #ff5722; font-size: 13px;">tools / functions</code>
</div>
</div>
<ul style="color: #666; font-size: 13px; margin-top: 15px; padding-left: 18px; line-height: 1.6;">
<li>Use <code>response_format</code> for structured JSON output (e.g., JSON Mode).</li>
<li>Use <b>Function Calling</b> for interacting with external tools and APIs.</li>
</ul>
</div>
The `response_format` follows the JSON Schema specification. Supported
types include:
- **`string`**: For text values
- **`number`**: For floating-point numbers
- **`integer`**: For whole numbers
- **`boolean`**: For true/false values
- **`object`**: For structured data with key-value pairs
- **`array`**: For lists of items
- **`null`**: To allow null values, add `"null"` to the type array
(e.g., `{"type": ["string", "null"]}`)
#### Type-Specific Properties
**For `object` values:**
- `properties`: Object mapping property names to their schema
definitions
- `required`: Array of required property names
- `additionalProperties`: Controls whether properties not in
`properties` are allowed
**For `string` values:**
- `enum`: List of specific possible string values for classification
- `format`: Specifies string syntax (e.g., `date-time`, `date`, `time`)
**For `number` and `integer` values:**
- `enum`: List of specific possible numeric values
- `minimum`: Inclusive minimum value
- `maximum`: Inclusive maximum value
**For `array` values:**
- `items`: Schema definition for all array elements
- `prefixItems`: List of schemas for the first N items (tuple-like
structures)
- `minItems`: Minimum number of items in the array
- `maxItems`: Maximum number of items in the array
json
{
"response_format": {
"type": "json_schema",
"properties": {
"response": {
"type": "string"
}
}
}
} - **Clear descriptions**: Use the `description` field in the schema to
clearly explain what each property means
- **Strong typing**: Use specific types (`integer`, `string`, `enum`)
whenever possible
- **Prompt engineering**: Clearly state in your prompt what you want the
model to extract or structure
- **Validation**: While structured output ensures JSON is syntactically
correct, always validate the semantic correctness of values in your
application code
operationId: gemini-2.5-flash-chat-completions
tags:
- docs/en/Market/Chat Models/Gemini
parameters: []
requestBody:
content:
application/json:
schema:
type: object
properties:
messages:
type: array
description: >-
An array of message objects. Each message has a role and
content.
**Unified Media File Format:**
In the content array, whether it's images, videos, audio, or
other document types, all media files use the same format
structure:
- The `type` field is always `"image_url"`
- The `image_url` field name remains unchanged
- The only thing that changes is the `url` value, which
points to the corresponding media file address
For example: images, videos, audio, PDFs, and other
documents all use the same `{ type: 'image_url', image_url:
{ url: '...' } }` structure.
items:
$ref: '#/components/schemas/Message'
minItems: 1
stream:
type: boolean
default: true
description: >-
If set to true, partial message deltas will be sent as
server-sent events. Default is true.
tools:
type: array
description: >-
An optional array of tools the model may call. The array can
contain multiple objects. Supports two formats:
1. **Google Search**: `{"type": "function", "function":
{"name": "googleSearch"}}` - Enables real-time information
retrieval via Google Search.
2. **Function calling**: Define your own functions with
name, description, and parameters. You can define multiple
functions in the array. Functions are defined using JSON
(specifically, a selected subset of OpenAPI schema format).
**Important**: Google Search and function calling are
mutually exclusive - you cannot use both in the same
request. When using function calling, you can include
multiple function definitions. Function calling and
`response_format` are also mutually exclusive - you cannot
use both in the same request.
items:
$ref: '#/components/schemas/Tool'
minItems: 0
include_thoughts:
type: boolean
description: >-
Whether to include thoughts in the response. If set to true,
thoughts will be included in the response, otherwise they
will not be included. Default is true.
default: true
response_format:
description: >-
Optional JSON Schema object defining the structure of the
response. When provided, the model will generate responses
that conform to this schema. **`response_format` and
function calling are mutually exclusive** - you cannot use
both in the same request.
Example:
```json
{
"type": "json_schema",
"properties": {
"response": {
"type": "string"
}
}
}
```
$ref: '#/components/schemas/ResponseFormat'
required:
- messages
x-apidog-orders:
- messages
- stream
- tools
- include_thoughts
- response_format
examples:
- messages:
- role: user
content:
- type: text
text: What is in this image?
- type: image_url
image_url:
url: >-
https://file.aiquickdraw.com/custom-page/akr/section-images/1759055072437dqlsclj2.png
tools:
- type: function
function:
name: googleSearch
stream: true
include_thoughts: true
response_format:
type: json_schema
properties:
response:
type: string
x-apidog-ignore-properties: []
example:
messages:
- role: user
content:
- type: text
text: What is in this image?
- type: image_url
image_url:
url: >-
https://file.aiquickdraw.com/custom-page/akr/section-images/1759055072437dqlsclj2.png
tools:
- type: function
function:
name: googleSearch
stream: true
include_thoughts: true
response_format:
type: json_schema
json_schema:
name: structured_output
strict: true
schema:
type: object
properties:
response:
type: string
responses:
'200':
description: >-
Request successful. When `response_format` is provided, the response
will conform to the specified JSON schema. Otherwise, returns the
standard chat completion format.
content:
application/json:
schema:
type: object
properties:
id:
type: string
description: Unique identifier for the chat completion
examples:
- chatcmpl-example-123
object:
type: string
description: Object type
examples:
- chat.completion
created:
type: integer
format: int64
description: Unix timestamp of when the completion was created
examples:
- 1677652288
model:
type: string
description: Model name
examples:
- gemini-2.5-flash
choices:
type: array
description: Array of completion choices
items:
type: object
properties:
index:
type: integer
description: Index of the choice
examples:
- 0
message:
type: object
properties:
role:
type: string
examples:
- assistant
content:
type: string
description: Message content
required:
- role
- content
x-apidog-orders:
- role
- content
x-apidog-ignore-properties: []
finish_reason:
type: string
description: Reason why the completion finished
examples:
- stop
required:
- index
- message
- finish_reason
x-apidog-orders:
- index
- message
- finish_reason
x-apidog-ignore-properties: []
usage:
type: object
properties:
prompt_tokens:
type: integer
description: Number of tokens in the prompt
examples:
- 10
completion_tokens:
type: integer
description: Number of tokens in the completion
examples:
- 50
total_tokens:
type: integer
description: Total number of tokens
examples:
- 60
required:
- prompt_tokens
- completion_tokens
- total_tokens
x-apidog-orders:
- prompt_tokens
- completion_tokens
- total_tokens
x-apidog-ignore-properties: []
x-apidog-orders:
- id
- object
- created
- model
- choices
- usage
x-apidog-ignore-properties: []
headers: {}
x-apidog-name: ''
'400':
description: Bad Request - Invalid request parameters
content:
application/json:
schema:
type: object
properties:
error:
type: object
properties:
message:
type: string
examples:
- Invalid request parameters
type:
type: string
examples:
- invalid_request_error
x-apidog-orders:
- message
- type
x-apidog-ignore-properties: []
x-apidog-orders:
- error
x-apidog-ignore-properties: []
headers: {}
x-apidog-name: ''
'401':
description: Unauthorized - Invalid or missing API key
content:
application/json:
schema:
type: object
properties:
error:
type: object
properties:
message:
type: string
examples:
- Unauthorized
type:
type: string
examples:
- authentication_error
x-apidog-orders:
- message
- type
x-apidog-ignore-properties: []
x-apidog-orders:
- error
x-apidog-ignore-properties: []
headers: {}
x-apidog-name: ''
'429':
description: Rate Limited - Too many requests
content:
application/json:
schema:
type: object
properties:
error:
type: object
properties:
message:
type: string
examples:
- Rate limit exceeded
type:
type: string
examples:
- rate_limit_error
x-apidog-orders:
- message
- type
x-apidog-ignore-properties: []
x-apidog-orders:
- error
x-apidog-ignore-properties: []
headers: {}
x-apidog-name: ''
'500':
description: request failed
content:
application/json:
schema:
type: object
properties:
code:
type: integer
description: >-
Response status code
- **200**: Success - Request has been processed
successfully
- **401**: Unauthorized - Authentication credentials are
missing or invalid
- **402**: Insufficient Credits - Account does not have
enough credits to perform the operation
- **404**: Not Found - The requested resource or endpoint
does not exist
- **408**: Upstream is currently experiencing service
issues. No result has been returned for over 10 minutes.
- **422**: Validation Error - The request parameters
failed validation checks
- **429**: Rate Limited - Request limit has been exceeded
for this resource
- **455**: Service Unavailable - System is currently
undergoing maintenance
- **500**: Server Error - An unexpected error occurred
while processing the request
- **501**: Generation Failed - Content generation task
failed
- **505**: Feature Disabled - The requested feature is
currently disabled
msg:
type: string
description: Response message, error description when failed
data:
type: object
properties: {}
x-apidog-orders: []
x-apidog-ignore-properties: []
x-apidog-orders:
- code
- msg
- data
required:
- code
- msg
- data
x-apidog-ignore-properties: []
example:
code: 500
msg: >-
Server Error - An unexpected error occurred while processing
the request
data: null
headers: {}
x-apidog-name: 'Error '
security: []
x-apidog-folder: docs/en/Market/Chat Models/Gemini
x-apidog-status: released
x-run-in-apidog: https://app.apidog.com/web/project/1184766/apis/api-28506435-run
components: schemas: ResponseFormat: type: object properties: type: type: string description: Only json_schema value json_schema: type: object properties: name: type: string description: Only structured_output value strict: type: boolean description: Enable strict mode? schema: type: object properties: type: type: string description: >- The response_format follows the JSON Schema specification. Supported types include:
string: For text values
number: For floating-point numbers
integer: For whole numbers
boolean: For true/false values
object: For structured data with key-value pairs
array: For lists of items
null: To allow null values, add "null" to the type array
properties:
type: object
properties:
response:
type: object
properties:
type:
type: string
required:
- type
x-apidog-orders:
- type
x-apidog-ignore-properties: []
required:
- response
x-apidog-orders:
- response
description: >-
Object mapping property names to their JSON Schema
definitions
x-apidog-ignore-properties: []
required:
type: array
items:
type: string
description: Array of required property names
title:
type: string
description: Short description of the schema
description:
type: string
description: Detailed description of the schema
required:
- type
- properties
- required
- title
- description
x-apidog-orders:
- type
- properties
- required
- title
- description
x-apidog-ignore-properties: []
required:
- name
- strict
- schema
x-apidog-orders:
- name
- strict
- schema
description: >-
JSON Schema object defining the structure of the response. When
provided, the model will generate responses that conform to this
schema.
x-apidog-ignore-properties: []
required:
- type
- json_schema
x-apidog-orders:
- type
- json_schema
title: chat model structured data structure
x-apidog-ignore-properties: []
x-apidog-folder: ''
Tool:
type: object
description: >-
Tool definition.
- **Enhanced Network Access**: `{"type": "function", "function":
{"name": "googleSearch"}}`
properties:
type:
type: string
enum:
- function
description: Utility type. Must be 'function'.
examples:
- function
function:
type: object
description: Function declarations for enhanced network access.
properties:
name:
type: string
description: Function name. Must be `googleSearch`.
description:
type: string
description: >-
Optional but recommended. A clear and specific description of
the function's purpose. Helps the model understand when to call
this function.
parameters:
type: object
description: >-
Defines a JSON Schema object for function parameters. Required
for custom functions; not used by 'googleSearch'. Follows the
JSON Schema specification.
properties:
type:
type: string
enum:
- object
description: Must be 'object' for function parameters
properties:
type: object
description: Map parameter names to objects defined in their JSON Schema.
additionalProperties:
type: string
x-apidog-orders: []
properties: {}
x-apidog-ignore-properties: []
required:
type: array
items:
type: string
description: Required parameter name array
required:
- type
- properties
x-apidog-orders:
- type
- properties
- required
x-apidog-ignore-properties: []
required:
- name
x-apidog-orders:
- name
- description
- parameters
x-apidog-ignore-properties: []
required:
- type
- function
x-apidog-orders:
- type
- function
title: The tools parameter of the chat model
x-apidog-ignore-properties: []
x-apidog-folder: ''
Message:
type: object
properties:
role:
type: string
enum:
- developer
- system
- user
- assistant
- tool
description: >-
Message role
- **developer**: Developer-provided instructions that the model
should follow, regardless of user messages. In o1 models and newer
versions, developer messages replace the previous system messages.
- **system**: Developer-provided instructions that the model should
follow, regardless of user messages. In o1 models and newer
versions, please use developer messages instead.
- **user**: Messages sent by end users, containing prompts or
additional context information.
- **assistant**: Messages sent by the model in response to user
messages.
- **tool**: Content of tool messages.
content:
type: array
description: >-
Message content array that can contain text and image objects.
**Unified Media File Format:**
Whether it's images, videos, audio, or other document types, all
media files use the same format structure:
- The `type` field is always `"image_url"`
- The `image_url` field name remains unchanged
- The only thing that changes is the `url` value, which points to
the corresponding media file address
For example: images, videos, audio, PDFs, and other documents all
use the same `{ type: 'image_url', image_url: { url: '...' } }`
structure.
items:
oneOf:
- type: object
properties:
type:
type: string
enum:
- text
examples:
- text
text:
type: string
description: 消息的文本内容
required:
- type
- text
x-apidog-orders:
- type
- text
x-apidog-ignore-properties: []
- type: object
properties:
type:
type: string
enum:
- image_url
examples:
- image_url
image_url:
type: object
properties:
url:
type: string
format: uri
description: 图像的 URL
required:
- url
x-apidog-orders:
- url
x-apidog-ignore-properties: []
required:
- type
- image_url
x-apidog-orders:
- type
- image_url
x-apidog-ignore-properties: []
required:
- role
- content
title: The messages parameter of the chat model
x-apidog-orders:
- role
- content
x-apidog-ignore-properties: []
x-apidog-folder: ''
securitySchemes: BearerAuth: type: bearer scheme: bearer bearerFormat: API Key description: |- 所有 API 都需要通过 Bearer Token 进行身份验证。
获取 API Key：
1. 访问 API Key 管理页面 获取您的 API Key
使用方法：
在请求头中添加：
Authorization: Bearer YOUR_API_KEY
注意事项：
- 请妥善保管您的 API Key，切勿泄露给他人
- 若怀疑 API Key 泄露，请立即在管理页面重置
BearerAuth1:
type: bearer
scheme: bearer
bearerFormat: API Key
description: |-
所有 API 都需要通过 Bearer Token 进行身份验证。
获取 API Key：
1. 访问 API Key 管理页面 获取您的 API Key
使用方法：
在请求头中添加：
Authorization: Bearer YOUR_API_KEY
注意事项：
- 请妥善保管您的 API Key，切勿泄露给他人
- 若怀疑 API Key 泄露，请立即在管理页面重置
servers:
- url: https://api.kie.ai description: 正式环境 security:
- BearerAuth: [] x-apidog: schemeGroups: - id: kn8M4YUlc5i0A0179ezwx schemeIds: - BearerAuth required: true use: id: kn8M4YUlc5i0A0179ezwx scopes: kn8M4YUlc5i0A0179ezwx: BearerAuth: []