Skip to content

Commit afecd62

Browse files
openrouter-docs-sync[bot]OpenRouter SDK Bot
andauthored
chore: update OpenAPI spec from monorepo (#1329)
Co-authored-by: OpenRouter SDK Bot <sdk-bot@openrouter.ai>
1 parent 60309c7 commit afecd62

1 file changed

Lines changed: 72 additions & 6 deletions

File tree

‎.speakeasy/in.openapi.yaml‎

Lines changed: 72 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -32257,6 +32257,61 @@ components:
3225732257
- 'type'
3225832258
- 'text'
3225932259
type: 'object'
32260+
ResponsesBadRequestResponse:
32261+
description: 'Bad Request - Invalid request parameters or malformed input. Request-shape validation failures carry a Responses API string code (e.g. `invalid_prompt`) with details in the top-level `metadata`; all other failures carry the integer HTTP status.'
32262+
example:
32263+
error:
32264+
code: 'invalid_prompt'
32265+
message: 'Invalid Responses API request'
32266+
metadata:
32267+
raw: '[{"code":"invalid_value","path":["input",0,"type"]}]'
32268+
properties:
32269+
error:
32270+
$ref: '#/components/schemas/ResponsesBadRequestResponseErrorData'
32271+
metadata:
32272+
additionalProperties:
32273+
type: 'string'
32274+
description: 'Validation details for string-coded errors; `raw` holds the serialized schema issues'
32275+
example:
32276+
raw: '[{"code":"invalid_value","path":["input",0,"type"]}]'
32277+
type:
32278+
- 'object'
32279+
- 'null'
32280+
openrouter_metadata:
32281+
additionalProperties: {}
32282+
type:
32283+
- 'object'
32284+
- 'null'
32285+
user_id:
32286+
type:
32287+
- 'string'
32288+
- 'null'
32289+
required:
32290+
- 'error'
32291+
type: 'object'
32292+
ResponsesBadRequestResponseErrorData:
32293+
description: 'Error data for ResponsesBadRequestResponse'
32294+
example:
32295+
code: 'invalid_prompt'
32296+
message: 'Invalid Responses API request'
32297+
properties:
32298+
code:
32299+
anyOf:
32300+
- type: 'integer'
32301+
- type: 'string'
32302+
description: 'Integer HTTP status, or a Responses API error code string (e.g. `invalid_prompt`) when the request body fails validation'
32303+
example: 'invalid_prompt'
32304+
message:
32305+
type: 'string'
32306+
metadata:
32307+
additionalProperties: {}
32308+
type:
32309+
- 'object'
32310+
- 'null'
32311+
required:
32312+
- 'code'
32313+
- 'message'
32314+
type: 'object'
3226032315
ResponsesErrorField:
3226132316
description: 'Error information returned from the API'
3226232317
example:
@@ -56971,13 +57026,24 @@ paths:
5697157026
'400':
5697257027
content:
5697357028
application/json:
56974-
example:
56975-
error:
56976-
code: 400
56977-
message: 'Invalid request parameters'
57029+
examples:
57030+
invalid-parameters:
57031+
summary: 'Invalid request parameters'
57032+
value:
57033+
error:
57034+
code: 400
57035+
message: 'Invalid request parameters'
57036+
invalid-request-body:
57037+
summary: 'Request body failed Responses API validation'
57038+
value:
57039+
error:
57040+
code: 'invalid_prompt'
57041+
message: 'Invalid Responses API request'
57042+
metadata:
57043+
raw: '[{"code":"invalid_value","path":["input",0,"type"]}]'
5697857044
schema:
56979-
$ref: '#/components/schemas/BadRequestResponse'
56980-
description: 'Bad Request - Invalid request parameters or malformed input'
57045+
$ref: '#/components/schemas/ResponsesBadRequestResponse'
57046+
description: 'Bad Request - Invalid request parameters or malformed input. Request-shape validation failures carry a Responses API string code (e.g. `invalid_prompt`) with details in the top-level `metadata`; all other failures carry the integer HTTP status.'
5698157047
'401':
5698257048
content:
5698357049
application/json:

0 commit comments

Comments
 (0)