.Net Core Web API -- 2

LOOKING FOR .NET CORE DEVELOPER – DYNAMIC WEB API FROM DATABASE DEFINITIONS

WE ARE LOOKING FOR AN EXPERIENCED ASP.NET CORE WEB API DEVELOPER TO BUILD A DYNAMIC, METADATA-DRIVEN API ENGINE.

PROJECT DESCRIPTION

WE MAINTAIN API DEFINITIONS INSIDE A SQL SERVER DATABASE.
EACH API RECORD INCLUDES:

- API CODE / ID
- SQL QUERY OR STORED PROCEDURE
- HTTP METHOD (GET / POST / PUT / DELETE)
- PARAMETER DEFINITIONS
- OUTPUT STRUCTURE

THE REQUIREMENT IS TO BUILD A .NET CORE WEB API THAT:

- ACCEPTS REQUESTS LIKE:

POST /API/EXECUTE/{APICODE}

- FETCHES API METADATA FROM DATABASE
- VALIDATES PARAMETERS DYNAMICALLY
- EXECUTES SQL SAFELY USING PARAMETERIZED QUERIES
- RETURNS JSON OUTPUT
- SUPPORTS PAGINATION, FILTERING, AND SORTING
- IMPLEMENTS PROPER ERROR HANDLING AND LOGGING
- USES AUTHENTICATION (JWT / API KEY)
- PREVENTS SQL INJECTION
- IS SCALABLE AND PRODUCTION READY

TECH STACK REQUIRED

- ASP.NET CORE WEB API (.NET 7 / .NET 8 PREFERRED)
- SQL SERVER
- DAPPER OR ENTITY FRAMEWORK CORE
- SWAGGER / OPENAPI
- JWT AUTHENTICATION
- CLEAN ARCHITECTURE / REPOSITORY PATTERN

EXPECTED DELIVERABLES

- COMPLETE SOURCE CODE
- DATABASE SCHEMA FOR API DEFINITIONS
- SAMPLE API CONFIGURATIONS IN DATABASE
- SWAGGER INTEGRATION
- DOCUMENTATION FOR ADDING NEW APIS DYNAMICALLY
- DEPLOYMENT GUIDE

IDEAL FREELANCER PROFILE

- STRONG EXPERIENCE WITH ASP.NET CORE WEB API
- EXPERIENCE IN METADATA-DRIVEN / DYNAMIC API SYSTEMS
- GOOD KNOWLEDGE OF SQL SERVER PERFORMANCE
- SECURITY BEST PRACTICES
- ENTERPRISE-LEVEL API DESIGN EXPERIENCE

WHEN APPLYING, PLEASE SHARE:

- SIMILAR PROJECTS YOU HAVE DONE
- GITHUB / PORTFOLIO LINK
- ESTIMATED TIMELINE
- COST QUOTE