Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

Overview

NpgsqlRest is a production-ready, standalone web server that automatically transforms your PostgreSQL database into a REST API. It provides:

  • Automatic HTTP REST endpoints from SQL files, functions, procedures, tables, and views
  • SQL files as endpoints — write plain .sql files containing PostgreSQL commands and get REST endpoints automatically
  • Code generation for JavaScript/TypeScript client libraries
  • Code generation for HTTP files for a simple way to quickly invoke and TEST your API.
  • Declarative configuration using SQL comments and annotations

To get started, you need:

  • A PostgreSQL database for metadata and endpoint specifications
  • Configuration via JSON files, environment variables, or command line arguments

Declarative Approach

NpgsqlRest uses SQL comment annotations to configure API endpoints declaratively. This approach keeps your API configuration close to your SQL logic.

NpgsqlRest creates REST endpoints from three types of sources:

Plain SQL Files Flagship

The primary way to create endpoints. Place .sql files containing PostgreSQL commands in a directory, and NpgsqlRest creates REST endpoints automatically. Parameter types and return columns are inferred via PostgreSQL's wire protocol — no functions, no procedures, no boilerplate:

sql
sql
-- sql/get_users.sql
-- HTTP GET
-- @authorize admin
-- @cached
-- @param $1 department_id
select id, name, email from users where department_id = $1;

This creates a GET /api/get-users?department_id=1 endpoint with authorization and caching.

Multi-command SQL files execute multiple statements in a single database round-trip:

sql
sql
-- sql/process_order.sql
-- HTTP POST
-- @param $1 order_id
-- @result validate
select count(*) from orders where id = $1;
update orders set status = 'processing' where id = $1;
-- @result confirm
select id, status from orders where id = $1;

See the SQL File Source configuration for details and the complete SQL File Source tutorial for a hands-on guide.

PostgreSQL Routines (Functions and Procedures)

NpgsqlRest also generates endpoints from PostgreSQL functions and procedures using the built-in COMMENT system:

sql
sql
create function get_user_data(id int)
returns table (name text, email text)
language sql
begin atomic;
select name, email from users where users.id = get_user_data.id;
end;

comment on function get_user_data(id int) is '
HTTP GET /admin/get-user-data
@authorize admin
Cache-Control: public, max-age=31536000';

This creates a GET endpoint at /admin/get-user-data that requires admin authorization and sets cache control headers.

Tables and Views (CRUD)

NpgsqlRest can also auto-generate CRUD endpoints for PostgreSQL tables and views:

sql
sql
comment on table users is 'HTTP';

This automatically generates REST endpoints for SELECT, INSERT, UPDATE, and DELETE operations on the users table. See CRUD Source configuration for details.

All three sources generate HTTP test files for testing your API and JavaScript/TypeScript client libraries with type definitions ready for your frontend.

Technology & Distribution

NpgsqlRest is built on the latest .NET with the Kestrel web server, compiled using AOT (Ahead-of-Time) compilation for:

  • Zero dependencies - single executable file
  • Fast startup - native performance
  • Cross-platform - runs on Windows, macOS, and Linux

Built on .NET/Kestrel, NpgsqlRest includes all modern web server capabilities out of the box, ensuring enterprise-grade performance and reliability.

NpgsqlRest is free and open-source, allowing you to:

  • Customize builds for specific platforms
  • Modify functionality to meet your needs
  • Contribute to the project's development

Comments