Skip to main content
Version: Next

Overview

In addition to the application server, Serverpod comes with a built-in web server. The web server allows you to access your database and business layer the same way you would from a method call from an app. This makes it simple to share data for applications that need both an app and traditional web pages. You can also use the web server to create webhooks or define custom REST APIs to communicate with third-party services.

Serverpod's web server is built on the Relic framework, giving you access to its routing engine, middleware system, and typed headers. This means you get the benefits of Serverpod's database integration and business logic alongside Relic's web server capabilities.

Your first route​

When you create a new Serverpod project, it sets up a web server by default. Here's how to add a simple API endpoint:

import 'package:serverpod/serverpod.dart';

class HelloRoute extends Route {
  @override
  Future<Result> handleCall(Session session, Request request) async {
    return Response.ok(
      body: Body.fromString(
        jsonEncode({'message': 'Hello from Serverpod!'}),
        mimeType: MimeType.json,
      ),
    );
  }
}

Register the route in your server.dart file before starting the server:

pod.webServer.addRoute(HelloRoute(), '/api/hello');
await pod.start();

Visit http://localhost:8080/api/hello to see your API response.

Core concepts​

Routes and handlers​

A Route is a destination in your web server that handles requests and generates responses. Routes extend the Route base class and implement the handleCall() method:

class ApiRoute extends Route {
  @override
  Future<Result> handleCall(Session session, Request request) async {
    // Your logic here
    return Response.ok();
  }
}

The handleCall() method receives:

  • Session - Access to your database, logging, and authenticated user
  • Request - The HTTP request with headers, body, and URL information

Response types​

Return different response types based on your needs:

// Success responses
return Response.ok(body: Body.fromString('Success'));
return Response.created(body: Body.fromString('Created'));
return Response.noContent();

// Error responses
return Response.badRequest(body: Body.fromString('Invalid input'));
return Response.unauthorized(body: Body.fromString('Not authenticated'));
return Response.notFound(body: Body.fromString('Not found'));
return Response.internalServerError(body: Body.fromString('Server error'));

Adding routes​

Routes are added with a path pattern:

// Exact path
pod.webServer.addRoute(UserRoute(), '/api/users');

// Path with wildcard
pod.webServer.addRoute(StaticRoute.directory(Directory('web')), '/static/**');

Routes are matched in the order they were added.

When to use what​

Rest apis → custom routes​

For REST APIs, webhooks, or custom HTTP handlers, use custom Route classes:

class UsersApiRoute extends Route {
  UsersApiRoute() : super(methods: {Method.get, Method.post});
  
  @override
  Future<Result> handleCall(Session session, Request request) async {
    if (request.method == Method.get) {
      // List users
    } else {
      // Create user
    }
  }
}

See Routing for details.

Static files → StaticRoute​

For serving CSS, JavaScript, images, or other static assets:

pod.webServer.addRoute(
  StaticRoute.directory(Directory('web/static')),
  '/static/**',
);

See Static Files for cache-busting and optimization.

Database access​

The Session parameter gives you full access to your Serverpod database:

class UserRoute extends Route {
  @override
  Future<Result> handleCall(Session session, Request request) async {
    // Query database
    final users = await User.db.find(session);
    
    // Use logging
    session.log('Retrieved ${users.length} users');
    
    return Response.ok(
      body: Body.fromString(
        jsonEncode(users.map((u) => u.toJson()).toList()),
        mimeType: MimeType.json,
      ),
    );
  }
}

Next steps​