add-api

name	add-api
description	Add a new API endpoint integration end-to-end — from endpoint definition through data source, model, repository, use case, and BLoC wiring. Use when connecting a new backend endpoint.

Add New API Endpoint

Connect a new backend endpoint end-to-end through all Clean Architecture layers.

When to Use

• User asks to integrate a new API endpoint
• User says "add API", "connect endpoint", "call backend"
• A new HTTP call needs to be added to an existing or new feature

Instructions

Family-Link uses Firebase heavily; adding “API” usually means repositories + services under lib/core/services/ and features/*/data/. See tech_readme_files/1_getting_started/PROJECT_ARCHITECTURE.md — if you add HTTP/Dio later, centralize it under lib/core/ and document it in tech_readme_files/.

Step 1 — Define Endpoint

In lib/core/api/api_endpoints.dart:

Static: static const String name = '/path'; Dynamic: static String name(int id) => '/path/$id';

Conventions:

• Group related endpoints under comment banners
• Paths do NOT include base URL or /api/v1 prefix

Step 2 — Add HTTP Call to Data Source

In the feature's data/datasources/*_remote_datasource.dart:

• Add method to abstract class
• Implement using ApiClient (get, post, put, patch, delete, uploadFile)
• Parse response with ApiResponse.fromJson()
• Return model(s)

Step 3 — Add/Update Model

If the API returns a new data shape:

• Create or update data/models/*_model.dart
• Extend entity, add fromJson/toJson
• Map backend snake_case keys

Step 4 — Update Domain Contract

Add method signature to abstract repository:

• Return type: Future<Either<Failure, T>>

Step 5 — Implement in Repository

In data/repositories/*_repository_impl.dart:

• Wrap in try/catch
• Map exceptions to failures (Auth, Network, Server, Unexpected)

Step 6 — Create Use Case

New file: domain/usecases/<action>_usecase.dart

• Extend UseCase<ReturnType, Params>
• Single responsibility

Step 7 — Wire into BLoC

• Add event class
• Add handler method
• Add state if needed
• For reads: wrap the fetch with CachePolicy.evaluate(cachedAt: ...) — return cached data if fresh/stale, only call API when stale (background) or expired
• For writes: check ConnectivityCubit state first; if offline, enqueue via OfflineQueue and emit an optimistic state instead of calling the API

Step 8 — Register in DI

In injection_container.dart:

• Register new use case as registerLazySingleton
• Update BLoC factory to inject new use case

API Response Reference

Success: { "success": true, "message": "...", "data": ..., "pagination": {...} } Error: { "success": false, "message": "...", "errors": {} } Validation (422): { "message": "...", "errors": { "field": ["msg"] } }

ApiClient Methods

Method	Signature
GET	apiClient.get(path, {queryParameters})
POST	apiClient.post(path, {data})
PUT	apiClient.put(path, {data})
PATCH	apiClient.patch(path, {data})
DELETE	apiClient.delete(path)
Upload	apiClient.uploadFile(path, {file, fieldName, data})