Add categories endpoint in API (#460)

* Add categories endpoint in API

* FIX eager load parent and subcategories associations

* FIX update specs to match

* Add rswag spec

* FIX openapi spec

* FIX final warns
This commit is contained in:
soky srm
2025-12-17 15:00:01 +01:00
committed by GitHub
parent 9d54719007
commit 7be799fac7
12 changed files with 924 additions and 16 deletions

139
docs/api/categories.md Normal file
View File

@@ -0,0 +1,139 @@
# Categories API Documentation
The Categories API allows external applications to retrieve financial categories within Sure. Categories are used to classify transactions and can be organized in a hierarchical structure with parent categories and subcategories. The OpenAPI description is generated directly from executable request specs, ensuring it always reflects the behaviour of the running Rails application.
## Generated OpenAPI specification
- The source of truth for the documentation lives in [`spec/requests/api/v1/categories_spec.rb`](../../spec/requests/api/v1/categories_spec.rb). These specs authenticate against the Rails stack, exercise every category endpoint, and capture real response shapes.
- Regenerate the OpenAPI document with:
```sh
SWAGGER_DRY_RUN=0 bundle exec rspec spec/requests --format Rswag::Specs::SwaggerFormatter
```
The task compiles the request specs and writes the result to [`docs/api/openapi.yaml`](openapi.yaml).
- Run just the documentation specs with:
```sh
bundle exec rspec spec/requests/api/v1/categories_spec.rb
```
## Authentication requirements
All category endpoints require an OAuth2 access token or API key that grants the `read` scope.
## Available endpoints
| Endpoint | Scope | Description |
| --- | --- | --- |
| `GET /api/v1/categories` | `read` | List categories with filtering and pagination. |
| `GET /api/v1/categories/{id}` | `read` | Retrieve a single category with full details. |
Refer to the generated [`openapi.yaml`](openapi.yaml) for request/response schemas, reusable components (pagination, errors), and security definitions.
## Filtering options
The `GET /api/v1/categories` endpoint supports the following query parameters for filtering:
| Parameter | Type | Description |
| --- | --- | --- |
| `page` | integer | Page number (default: 1) |
| `per_page` | integer | Items per page (default: 25, max: 100) |
| `classification` | string | Filter by classification: `income` or `expense` |
| `roots_only` | boolean | Return only root categories (categories without a parent) |
| `parent_id` | uuid | Filter subcategories by parent category ID |
## Category object
A category response includes:
```json
{
"id": "uuid",
"name": "Food & Drink",
"classification": "expense",
"color": "#f97316",
"icon": "utensils",
"parent": null,
"subcategories_count": 2,
"created_at": "2024-01-15T10:30:00Z",
"updated_at": "2024-01-15T10:30:00Z"
}
```
## Category hierarchy
Categories support a two-level hierarchy:
- **Root categories** (parent categories) have `parent: null` and may have subcategories
- **Subcategories** have a `parent` object containing the parent's `id` and `name`
Example subcategory response:
```json
{
"id": "uuid",
"name": "Restaurants",
"classification": "expense",
"color": "#f97316",
"icon": "utensils",
"parent": {
"id": "uuid",
"name": "Food & Drink"
},
"subcategories_count": 0,
"created_at": "2024-01-15T10:30:00Z",
"updated_at": "2024-01-15T10:30:00Z"
}
```
## Classification types
Categories are classified into two types:
| Classification | Description |
| --- | --- |
| `income` | Categories for income transactions (salary, investments, etc.) |
| `expense` | Categories for expense transactions (food, utilities, etc.) |
Subcategories inherit the classification of their parent category.
## Filtering examples
### Get all expense categories
```
GET /api/v1/categories?classification=expense
```
### Get only root categories (no subcategories)
```
GET /api/v1/categories?roots_only=true
```
### Get subcategories of a specific parent
```
GET /api/v1/categories?parent_id=<parent-category-uuid>
```
### Combine filters with pagination
```
GET /api/v1/categories?classification=expense&roots_only=true&page=1&per_page=10
```
## Error responses
Errors conform to the shared `ErrorResponse` schema in the OpenAPI document:
```json
{
"error": "error_code",
"message": "Human readable error message"
}
```
Common error codes include `unauthorized`, `not_found`, and `internal_server_error`.