▸case-01 I am building a web service for an e-commerce platform and need to design the API contract before writing code. Could you create a complete OpenAPI 3.1 specification in YAML for our product catalog service? It should include endpoints for searching products, creating new items, and updating stock levels, complete with request bodies and standard HTTP response schemas. | fail→fail | 57,975 | 57,713 | -0% | 1 | 1 | 0% | 5,862 | 5,975 | +2% | 0 | 0 | — |
▸case-02 We have an existing backend with endpoints for authentication and user profile management (`/auth/login`, `/auth/register`, `/users/me`), but we lack formal documentation. Please generate a valid OpenAPI 3.1 JSON definition file covering paths, parameter specifications, security schemes, and error response models for these routes. | fail→fail | 24,936 | 23,059 | -8% | 1 | 1 | 0% | 5,452 | 5,185 | -5% | 0 | 0 | — |
▸case-03 I'm working on an internal API draft for a notification system that handles email and SMS alerts, but I want to make sure it is compliant with current standards. Please review my route details, supply a fully corrected OpenAPI 3.1 document, and provide a structured verification checklist to ensure our implementation matches the specification. | fail→fail | 25,642 | 25,086 | -2% | 1 | 1 | 0% | 4,945 | 5,213 | +5% | 0 | 0 | — |
▸case-04 We are migrating our API layer from REST to GraphQL for our mobile app client. Please design a complete GraphQL schema file using Schema Definition Language (SDL) for a social feed service with user profiles, posts, and nested comments. | pass→pass | 19,680 | 16,355 | -17% | 1 | 1 | 0% | 3,552 | 3,402 | -4% | 0 | 0 | — |
▸case-05 We are building a high-performance inter-service communication system using gRPC. Please write a Protocol Buffers v3 (.proto) definition file for an inventory management service with streaming RPCs for stock updates. | pass→pass | 17,463 | 17,255 | -1% | 1 | 1 | 0% | 3,232 | 3,386 | +5% | 0 | 0 | — |
▸case-06 I need to configure Nginx as a reverse proxy for our REST backend running on port 8080. Please provide an nginx.conf block that handles SSL termination, routes /api/v1 traffic, and sets up client rate limiting at 100 requests per minute. | pass→pass | 14,668 | 14,046 | -4% | 1 | 1 | 0% | 2,794 | 2,943 | +5% | 0 | 0 | — |
▸case-07 We are creating an OpenAPI 3.1 YAML specification for our user profile API. In older OpenAPI 3.0 specs, we used nullable: true for fields that accept null values. Should we continue using nullable: true in our OpenAPI 3.1 schemas, or how should nullability be represented? Provide the correct syntax. | pass→pass | 12,329 | 9,518 | -23% | 1 | 1 | 0% | 2,145 | 1,994 | -7% | 0 | 0 | — |
▸case-08 Our payment processing gateway sends asynchronous HTTP callbacks (webhooks) to client endpoints when subscriptions are renewed. We want to document these incoming webhook requests in our OpenAPI contract. Should webhooks be placed under the paths object or somewhere else in OpenAPI 3.1? Provide an example skeleton. | pass→pass | 9,507 | 12,482 | +31% | 1 | 1 | 0% | 1,696 | 2,356 | +39% | 0 | 0 | — |
▸case-09 We have drafted an OpenAPI 3.1 specification file named openapi.yaml for our logistics tracking API. What tool and terminal command should we execute to lint this specification file against standard OpenAPI rules and report syntax or structure errors? | pass→pass | 7,685 | 5,569 | -28% | 1 | 1 | 0% | 1,253 | 1,170 | -7% | 0 | 0 | — |
▸case-10 We have a validated OpenAPI 3.1 specification file located at api-spec.json. We want to automatically generate a TypeScript client library for frontend developers. What CLI tool and invocation command should we use to accomplish this task? | pass→pass | 10,070 | 9,083 | -10% | 1 | 1 | 0% | 1,699 | 1,781 | +5% | 0 | 0 | — |
▸case-11 We want to host an interactive HTML documentation website for our developer portal using our openapi.yaml spec file. What open-source frontend renderer libraries or tools can generate static or dynamic HTML documentation from an OpenAPI 3.1 document? | pass→pass | 21,171 | 18,709 | -12% | 1 | 1 | 0% | 3,580 | 3,422 | -4% | 0 | 0 | — |
▸case-12 Our backend team wants to adopt a design-first API approach for a new billing microservice covering invoice creation and retrieval. We haven't specified the exact field types for tax calculations, currency codes, or discount line items. Should you generate the full OpenAPI 3.1 spec immediately with guessed defaults, or what step should be taken first? | pass→pass | 10,062 | 10,716 | +6% | 1 | 1 | 0% | 1,585 | 2,043 | +29% | 0 | 0 | — |
▸case-13 We need to document OAuth2 authorization in our OpenAPI 3.1 specification for a cloud storage API. The API uses Authorization Code flow with PKCE and token endpoint https://auth.example.com/oauth/token. How should the securitySchemes section in components be structured? | pass→pass | 10,630 | 8,550 | -20% | 1 | 1 | 0% | 1,875 | 1,755 | -6% | 0 | 0 | — |
▸case-14 In our pet store API contract, an endpoint returns generic Animal objects that can be either a Dog or a Cat. We want to use OpenAPI 3.1 polymorphism so client SDK generators can map the payload to exact classes using a type property. Show how to model this in OpenAPI 3.1. | pass→pass | 14,371 | 10,697 | -26% | 1 | 1 | 0% | 2,580 | 2,228 | -14% | 0 | 0 | — |
▸case-15 Our REST API hosted at https://api.example.com has multiple deployment environments (production, staging, sandbox). We want to declare server URLs dynamically in our OpenAPI 3.1 file using server variables. Show how the servers object should be structured. | pass→pass | 13,622 | 14,772 | +8% | 1 | 1 | 0% | 2,406 | 2,719 | +13% | 0 | 0 | — |
▸case-16 Our API has standard HTTP 400 Bad Request and HTTP 500 Internal Error response objects repeated across 15 endpoints. How should these reusable response schemas be defined in an OpenAPI 3.1 YAML document to prevent duplication? | pass→pass | 11,365 | 12,657 | +11% | 1 | 1 | 0% | 2,098 | 2,593 | +24% | 0 | 0 | — |
▸case-17 We are building a file upload endpoint POST /files/upload that accepts both multipart/form-data with a binary file plus metadata, and application/json for bulk metadata updates. How should requestBody be specified in OpenAPI 3.1? | pass→pass | 13,233 | 12,627 | -5% | 1 | 1 | 0% | 2,383 | 2,482 | +4% | 0 | 0 | — |
▸case-18 We created an OpenAPI 3.1 spec for our order management service. Before writing the actual backend code, our frontend developers need a local mock server that returns realistic mock responses matching our schema and validates request payloads. What tool can act as a mock server directly from an OpenAPI 3.1 file? | pass→pass | 13,740 | 11,011 | -20% | 1 | 1 | 0% | 2,172 | 1,956 | -10% | 0 | 0 | — |
▸case-19 We want to secure our REST API endpoints using an API key passed in an HTTP header named X-API-Key. How do we declare this authentication method in the securitySchemes and apply it globally in OpenAPI 3.1? | pass→pass | 8,898 | 6,357 | -29% | 1 | 1 | 0% | 1,571 | 1,364 | -13% | 0 | 0 | — |
▸case-20 Our GET /reports/{id} endpoint can return either application/pdf or application/json. Additionally, response headers must return X-RateLimit-Remaining. How should this response be defined in OpenAPI 3.1 YAML? | pass→pass | 10,844 | 9,773 | -10% | 1 | 1 | 0% | 2,030 | 2,080 | +2% | 0 | 0 | — |
▸case-21 We have a code-first Python application built with FastAPI. We want to export the automatically generated OpenAPI 3.1 specification to a JSON file named openapi.json for validation in our CI/CD pipeline. What Python script or command extracts the spec directly from the FastAPI app instance? | pass→pass | 11,912 | 8,582 | -28% | 1 | 1 | 0% | 1,794 | 1,743 | -3% | 0 | 0 | — |
▸case-22 Please create an OpenAPI 3.1 spec for a search endpoint GET /search. I haven't decided what query parameters to support, whether results should be paginated using cursor or limit/offset, or what fields the search hit schema should contain. Generate the specification now. | fail→fail | 20,719 | 16,591 | -20% | 1 | 1 | 0% | 3,981 | 3,250 | -18% | 0 | 0 | — |