Design and implement RESTful API endpoints following best practices for routing, versioning, and HTTP standards. Use this skill when creating or modifying API routes, controllers, or endpoints in files like routes/api.php, API controller files in app/Http/Controllers/Api/, controller files in app/Http/Controllers/, API resource classes, or when implementing REST API functionality. Use when working on URL structures, HTTP method handling (GET, POST, PUT, PATCH, DELETE), API versioning strategi...
Installs into .claude/skills of the current project.
Are you the author of Backend Api?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-backend-api)
---
name: backend-api
description: Design and implement RESTful API endpoints following best practices for routing, versioning, and HTTP standards. Use this skill when creating or modifying API routes, controllers, or endpoints in files like routes/api.php, API controller files in app/Http/Controllers/Api/, controller files in app/Http/Controllers/, API resource classes, or when implementing REST API functionality. Use when working on URL structures, HTTP method handling (GET, POST, PUT, PATCH, DELETE), API versioning strategies, query parameter handling for filtering/sorting/pagination, HTTP status code responses, rate limiting configuration, or any API endpoint design decisions.
---
# Backend API
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle backend API.
## When to use this skill
- When creating or editing API route definitions in `routes/api.php` or similar routing files
- When building or modifying controllers in `app/Http/Controllers/` or controller directories
- When building or modifying API controllers in `app/Http/Controllers/Api/` or API-specific controller directories
- When implementing RESTful endpoints with proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
- When designing URL structures and resource-based API paths
- When implementing API versioning (URL path versioning like `/api/v1/` or header-based versioning)
- When configuring query parameters for filtering, sorting, pagination, or search functionality
- When determining appropriate HTTP status codes for API responses (200, 201, 400, 404, 500, etc.)
- When implementing rate limiting headers or API throttling
- When creating nested resource routes or working with resource relationships in APIs
- When writing API resource transformation classes or response formatting logic
## Instructions
For details, refer to the information provided in this file:
[backend API](../../../agent-os/standards/backend/api.md)
