ABP Framework — API Development

What problem does it solve?

ABP developers need a reliable way to turn application services into REST endpoints and clients without writing repetitive controller and HTTP plumbing by hand.

Core Features & Use Cases

• Auto API Controllers (Conventions): Automatically expose application services as REST controllers via conventional routing (e.g., method-to-HTTP mapping and route computation under /api/app by default).
• Dynamic & Static C# HTTP Client Proxies: Generate or create runtime proxies that call remote ABP endpoints with correct serialization, auth headers, and ABP-specific metadata.
• Swagger + API Versioning + Integration Services: Produce discoverable OpenAPI docs, support multiple API versions, and enable module-to-module integration via IIntegrationService instead of HTTP.

Use case: You build a modular ABP system where you want BookAppService endpoints exposed as REST APIs, consumed by a separate client module using generated proxies, with Swagger docs and predictable versioned routes.

Quick Start

Implement conventional API controller exposure for your ABP module and configure a client proxy so the AI can generate the required controller, routes, and HTTP client usage for API endpoints in ABP v10.4.