React/.NET API Integration Developer with DOTNET experience to develop backend
Budget: ₹12,500 – ₹37,500 INR
The project’s front-end designs are already mapped out in Figma and the React codebase is in place, but the heart of the application—the .NET back-end—still needs to be built out and wired to multiple APIs. I need help turning that blank canvas into a secure, well-structured REST layer that the React client can rely on.
Your main mission is to design and implement the entire server side in .NET (Core 6 or later is fine), then expose clean, versioned endpoints that cover:
• User authentication and role-based authorization
• Fast, reliable data storage and retrieval (SQL Server or a lightweight alternative—whatever fits)
• All business-logic processing, kept neatly behind service interfaces
Along the way we’ll be integrating three categories of APIs—third-party, internal, and a small set of custom-built services—so experience juggling different auth schemes, rate limits, and payload formats will be invaluable.
On the front-end, you’ll connect the finished endpoints to the existing React components, keeping the UX faithful to the Figma layouts while ensuring state management and error handling feel seamless to users.
Deliverables I expect:
1. Complete .NET solution with unit tests and clear project structure
2. Integrated API wrappers with sensible retry / timeout policies
3. Updated React code that consumes the new endpoints
4. A concise README covering setup, environment variables, and deployment steps
If you’ve shipped similar React-plus-.NET stacks and enjoy untangling complex integrations, this should be straightforward. Let me know your preferred approach to auth, data layer, and API resilience so we can kick things off quickly.
Your main mission is to design and implement the entire server side in .NET (Core 6 or later is fine), then expose clean, versioned endpoints that cover:
• User authentication and role-based authorization
• Fast, reliable data storage and retrieval (SQL Server or a lightweight alternative—whatever fits)
• All business-logic processing, kept neatly behind service interfaces
Along the way we’ll be integrating three categories of APIs—third-party, internal, and a small set of custom-built services—so experience juggling different auth schemes, rate limits, and payload formats will be invaluable.
On the front-end, you’ll connect the finished endpoints to the existing React components, keeping the UX faithful to the Figma layouts while ensuring state management and error handling feel seamless to users.
Deliverables I expect:
1. Complete .NET solution with unit tests and clear project structure
2. Integrated API wrappers with sensible retry / timeout policies
3. Updated React code that consumes the new endpoints
4. A concise README covering setup, environment variables, and deployment steps
If you’ve shipped similar React-plus-.NET stacks and enjoy untangling complex integrations, this should be straightforward. Let me know your preferred approach to auth, data layer, and API resilience so we can kick things off quickly.
Related categories:
.NET
C# Programming
ASP.NET
Microsoft SQL Server
RESTful
.NET Core
API Development
.NET 5.0/6