RTS Questionnaire · Question 28 of 52 · file: answers/q28.html
Have you designed and implemented RESTful APIs using .NET?
.NETRESTAPI
✅ Yes — I have designed and implemented RESTful APIs in .NET/ASP.NET Core, from endpoints and contracts through security, testing and deployment.
🧪 Interactive proof: this answer has its own page with a live REST design workflow, the published contract, the ASP.NET Core endpoints and the contract tests behind it — open the Q28 REST API proof →
Technical detail
- 📐 Design first — resource-oriented modelling, correct HTTP semantics (verbs, status codes, idempotency of PUT/DELETE), pagination/filtering/sorting conventions, HATEOAS-style links where useful, and consistent error payloads using
ProblemDetails. - 🛠️ Implementation — controller-based and minimal-API endpoints, async/await throughout, clean separation of DTOs and domain models, data access via EF Core or Dapper,
IHttpClientFactoryfor outbound integrations, and background processing for long-running work. - 🔐 Security and resilience — JWT bearer/OAuth2 authorization with policy and claim checks, input validation, CORS allow-lists, rate limiting and throttling, request size limits, retry/circuit-breaker policies for downstream calls, and structured audit logging.
- 📚 Contract and documentation — Swagger/OpenAPI generation with examples and auth flows, so QA and front-end teams (Angular clients) integrate against a reliable contract; typed clients generated for the SPA.
- 🧪 Verification — unit tests for handlers, integration tests through
WebApplicationFactoryagainst a real database container, and performance checks on hot endpoints; deployment via container images and CI/CD pipelines with health checks and observability endpoints.
🧾 CV evidence: CV .NET Technologies: 'Web API', 'REST in .NET', ASP.NET Core, Dependency Injection; 2025 DMS .NET assessment (controllers/services, Swagger, JWT, SQL) with Angular SPA consuming the API.