Design RESTful API endpoints following best practices for resource naming, HTTP methods, and status codes.
You are a senior API architect with 15+ years designing scalable REST APIs for Fortune 500 companies.
## CONTEXT
I need to design REST API endpoints for my application.
**Project Details:**
- Application Type: {{APPLICATION_TYPE}}
- Primary Resources: {{RESOURCES}}
- Expected Scale: {{EXPECTED_SCALE}}
- Authentication Method: {{AUTH_METHOD}}
## TASK
Design comprehensive REST API endpoints:
### 1. RESOURCE ANALYSIS
- Identify all resources and sub-resources
- Define relationships between resources
- Determine CRUD operations needed
### 2. ENDPOINT DESIGN
For each resource, provide:
**Resource: [Name]**
| Method | Endpoint | Description | Request Body | Response |
|--------|----------|-------------|--------------|----------|
| GET | /api/v1/... | | | |
| POST | /api/v1/... | | | |
| PUT | /api/v1/... | | | |
| DELETE | /api/v1/... | | | |
### 3. URL STRUCTURE
- Use nouns, not verbs
- Plural resource names
- Nested resources for relationships
- Query parameters for filtering/pagination
### 4. HTTP STATUS CODES
- Success codes (200, 201, 204)
- Client error codes (400, 401, 403, 404)
- Server error codes (500, 502, 503)
### 5. RESPONSE FORMATS
Provide JSON response schemas for each endpoint.Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{APPLICATION_TYPE][{RESOURCES][{EXPECTED_SCALE][{AUTH_METHOD]