Results for “api-resources”

Design consistent, developer-friendly REST APIs with conventions for resource naming, HTTP methods, status codes, pagination, filtering, error responses, versioning, and rate limiting.

Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.

Design REST and GraphQL APIs with OpenAPI 3.1 specifications, resource modeling, versioning strategies, pagination patterns, and error handling standards.

REST API design — resource naming, HTTP methods, status codes, pagination, versioning, OpenAPI. Use when designing a new REST API, reviewing API contracts, writing OpenAPI/Swagger documentation, or choosing pagination, versioning, or error-format strategies.

Generates OpenAPI 3.1 documentation from an API codebase, auto-detecting frameworks, extracting routes and schemas, and setting up interactive docs.

Write API documentation including endpoint references, OpenAPI/Swagger specs, authentication guides, SDK quickstarts, and interactive code samples. Use when documenting REST APIs, GraphQL schemas, WebSocket interfaces, or SDK libraries. Also trigger for 'API docs', 'endpoint documentation', 'OpenAPI', 'Swagger', 'SDK documentation', 'API reference', or 'REST docs'.

Design RESTful and GraphQL APIs with proper validation, versioning, and documentation. Use when creating new endpoints, designing request/response models, or reviewing API contracts.

Design APIs with endpoints, methods, and documentation. TRIGGERS - Use when user needs help with api-design related tasks.

Designs scalable REST and GraphQL APIs, creates OpenAPI 3.1 specifications, and plans versioning, pagination, and error handling.

Design APIs with endpoints, methods, and documentation. TRIGGERS - Use when user needs help with api-design related tasks.