![[interface] image of game elements](https://cdn.prod.website-files.com/685543d741486e66fdf76f76/68554455da50c670bb18b225_df499286-c3b6-4b56-8c33-a0093c329d5f.avif)
Build secure, standards-compliant APIs based on your SQL Server.
Publish internally or on the public internet with full customization.
No Code. Full Control. Self-Hosted.
Mappings between database objects and the API are stored in the objects’ metadata, so the API definitions follow the database objects even when their names or structures change. When creating endpoints and data models, you can fully customize paths, resource names, columns, and parameters.
Configure authentication, documentation, rate limits, logging, telemetry, headers, CORS, compression, pagination, caching, security, request types, and more.
Adapt every aspect to your API needs.
![[interface] image of a laptop displaying product interface (for an ai saas company)](https://cdn.prod.website-files.com/685543d741486e66fdf76f76/68554455691d8adc81c7e5af_bdb22c48-bfb3-4c2e-b786-6f4b8dabaa35.avif)
The server automatically generates detailed documentation compliant with the OpenAPI specification.
Swagger UI automatically renders the documentation at the selected API endpoint. You can define the descriptions of every API element yourself, thereby shaping the final documentation.
Build secure, standards-compliant APIs – self-hosted.
Publish internally or on the public internet with full customization, robust authentication, and seamless mapping.
Deploy securely on your own infrastructure. Your database is never exposed directly. Maintain full control and compliance at all times.
Mappings between database objects and the API are stored in the objects’ metadata, so the API definitions follow the database objects even when their names or structures change.
The server automatically generates detailed documentation compliant with the OpenAPI specification. Swagger UI automatically renders the documentation at the selected API endpoint.You can define the descriptions of every API element yourself, thereby shaping the final documentation.
SQL Server - with its defined users and roles - acts as the identity source, while secure, encrypted authentication is handled through JWT tokens.
You can expose tables and views through the API, and for more complex scenarios you can also expose stored procedures.
Expose file folders through the API so users can seamlessly upload and download files.
You can define CORS policies and apply them to specific API endpoints.
You can define rate limiters that restrict how many requests can be sent to the API. Limiters can be configured for different time windows and according to various criteria (e.g., IP address, user login, or authentication level).
Enable full request-and-response logging, either to a database or to popular services like Treblle or Sentry. You can also enable OpenTelemetry (OTLP-compliant) telemetry.
Define response headers that are added to every API call - especially helpful for enforcing security headers and browser policies.
Enable compression for API responses with Brotli or Gzip to minimize payload size and improve performance.
Instantly preview your generated API in a Swagger UI-rendered OpenAPI view. Create as many API projects as you need, plug into multiple databases, and spin up multiple production instances with ease.
For each API endpoint, you can configure caching mechanisms on both the server and client sides.
Enable pagination for large datasets to reduce resource usage on both server and client.
Define which roles have access to each endpoint and which HTTP methods they may use.
Define the list of supported HTTP methods for each endpoint.
Define table primary keys flexibly so they are respected in GET methods.
Extend GET methods with parameters for column-level filtering, sorting, and selective field projection.
No-cost
For Testing Purposes
Features
Max 3 Tables
Max 3 Views
Max 3 Stored Procedures
Max 3 File Folders
Per year
Single Machine License
Features
Unlimited Tables
Unlimited Views
Unlimited Stored Procedures
Unlimited File Folders
Tailored deployments, dedicated support, custom integrations.
Apizzer targets Microsoft SQL Server 2012 and newer, including Azure SQL. By focusing on a single engine, it can fully use SQL Server-specific features - without the compromises you usually face with tools that try to support many databases.
Authentication is based on JWT tokens issued for native SQL Server logins; authorization re-uses existing database roles. Designer lets you configure per-endpoint role matrices, fine-grained CORS, and rate limits.
The Web API is stateless, so horizontal scaling is straightforward: start multiple instances and place them behind a reverse proxy or load balancer.
You can publish v1 of the API, keep it running, then clone the project in Designer, bump the version (e.g., 2.0.0), and publish to a different base URL such as /api/v2. Both versions can coexist until consumers migrate.
Yes. Any stored procedure can be surfaced as a single endpoint and bound to any HTTP verb you choose. You control which parameters are public, how they’re named, where they appear (route, query, or body), and you can design a typed response model so Swagger / OpenAPI documents the result set precisely.
Map SQL Server to secure, standards-compliant APIs.
No code. Full control.
