REST API design
Reusable endpoints that several product modules can share, rather than each feature accumulating its own near-duplicate routes.
Available for contract, freelance and full-time engagements
Node.js & Nest.js API Development
An API is the part of a product with the longest life and the highest cost of getting wrong. I build REST APIs on Nest.js and Express with typed contracts, real authorisation boundaries, and the slow work pushed onto background queues where it belongs.
What this covers
Background processing
BullMQ job queues for work too slow for a request cycle — the FFmpeg video transcoding pipeline behind Vistana is built this way.
Third-party integration
Secure OAuth proxies that keep credentials server-side and normalise upstream responses, so provider changes stop at the integration layer instead of reaching your frontend.
Authorisation and rate limiting
Multi-role permission models and Redis-based rate limiting on endpoints that are expensive to serve.
Tools and technologies
Node.jsNest.jsExpress.jsTypeScriptBullMQRedisPostgreSQLMongoDBPrisma ORM
Proof of work
Projects where I have already done this, written up as case studies.
VoxBox Marketing
AI-powered customer engagement platform automating conversations, leads and marketing workflows.
Read case study: VoxBox MarketingVistana
Browser-based screen recording and instant video sharing, built end to end.
Read case study: Vistanasmart-audio-diff
Published TypeScript library for diffing WAV audio files and their transcripts.
Read case study: smart-audio-diffInsider Analytics Integration
Real-time soccer player-performance analytics behind a secure Node.js OAuth proxy.
Read case study: Insider Analytics IntegrationBlogspot API
REST APIs for a blogging platform with secure multi-role operations.
Read case study: Blogspot APISelf-Photos API
REST APIs for automatic device-to-local-storage photo backup.
Read case study: Self-Photos APIQuestions
Nest.js or Express for a new API?
Nest.js once the API will grow beyond a few modules — the imposed structure and dependency injection stop it turning into a pile of route handlers. Express when the surface is genuinely small. I have shipped production systems on both.
Can you integrate a third-party API securely?
Yes. For the Insider sports analytics integration I built a Node.js OAuth proxy that keeps API credentials server-side and normalises responses, so the frontend consumes a stable shape regardless of upstream changes.
How do you handle slow operations like video processing?
Off the request path, onto a queue. Vistana runs FFmpeg transcoding through BullMQ background jobs, so the API stays responsive while processing happens asynchronously and the client polls for status.
Other services
LET'S TALK SPECIFICS
If node.js api development is what you need, tell me about the system, the constraints and the timeline.