Receber por email
← Voltar para o catálogo

rest-api-design

RESTful API design principles, versioning, pagination, HATEOAS, and documentation.

1.4kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add a5c-ai/babysitter

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/rest-api-design/svg)](https://www.skillteca.com.br/skills/rest-api-design)

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

REST API Design Skill

Expert assistance for designing RESTful APIs following best practices.

Capabilities

  • Design resource-oriented APIs
  • Implement proper HTTP methods and status codes
  • Configure API versioning strategies
  • Implement pagination patterns
  • Design error responses
  • Apply HATEOAS principles

Usage

Invoke this skill when you need to:

  • Design new REST APIs
  • Review existing API design
  • Implement pagination
  • Define error handling
  • Version APIs

Design Principles

Resource Naming

# Good - nouns, plural
GET /api/users
GET /api/users/123
GET /api/users/123/posts

# Bad - verbs, actions in URL
GET /api/getUsers
GET /api/users/123/getPosts
POST /api/createUser

HTTP Methods

| Method | Usage | Response | |--------|-------|----------| | GET | Read resource | 200 OK | | POST | Create resource | 201 Created | | PUT | Replace resource | 200 OK | | PATCH | Partial update | 200 OK | | DELETE | Remove resource | 204 No Content |

Pagination Response

{
  "data": [...],
  "meta": {
    "page": 1,
    "limit": 10,
    "total": 100,
    "totalPages": 10
  },
  "links": {
    "self": "/api/users?page=1",
    "next": "/api/users?page=2",
    "prev": null
  }
}

Error Response

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Validation failed",
    "details": [
      { "field": "email", "message": "Invalid email format" }
    ]
  }
}

Best Practices

  • Use proper HTTP status codes
  • Implement consistent error responses
  • Version APIs from the start
  • Document with OpenAPI

Target Processes

  • api-design
  • backend-development
  • microservices-architecture
Compartilhar X LinkedIn