Prompt Details
Model
(gemini-3.1-pro)
Token size
321
Example input
[Endpoint Path]: /users/{userId}
[HTTP Method]: GET
[Logic]: Fetch user profile details including name, email, and account status.
Example output
openapi: 3.0.0
info:
title: API Specification
version: 1.0.0
paths:
/users/{userId}:
get:
summary: Get user profile
description: Fetch user profile details including name, email, and account status.
operationId: getUserProfile
parameters:
- name: userId
in: path
required: true
description: Unique identifier of the user
schema:
type: string
example: "usr_12345abc"
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
id:
type: string
example: "usr_12345abc"
name:
type: string
example: "John Doe"
email:
type: string
format: email
example: "john.doe@example.com"
status:
type: string
enum: [active, suspended, pending]
example: "active"
'400':
description: Bad Request - Invalid userId format
'401':
description: Unauthorized - Missing or invalid token
'404':
description: Not Found - User does not exist
'500':
description: Internal Server Error
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
6
Views
GEMINI-3.1-PRO
Stop writing tedious API documentation by hand. This prompt acts as a Senior Backend Engineer, converting your basic endpoint descriptions or raw code logic into perfectly formatted, production-ready OpenAPI (Swagger) 3.0 specifications in YAML. It automatically generates schemas, query parameters, request bodies, and standard error responses, saving hours of manual formatting.
...more
Added over 1 month ago
