Routes options

  • : currently it supports 'DELETE', 'GET', 'HEAD', 'PATCH', 'POST', 'PUT' and 'OPTIONS'. It could also be an array of methods.

  • url: the path of the URL to match this route (alias: path).

  • schema: an object containing the schemas for the request and response. They need to be in format, check here for more info.

    • body: validates the body of the request if it is a POST, PUT, or PATCH method.
    • querystring or query: validates the querystring. This can be a complete JSON Schema object, with the property type of object and properties object of parameters, or simply the values of what would be contained in the properties object as shown below.
    • params: validates the params.
    • response: filter and generate a schema for the response, setting a schema allows us to have 10-20% more throughput.

  • exposeHeadRoute: creates a sibling HEAD route for any GET routes. Defaults to the value of instance option. If you want a custom HEAD handler without disabling this option, make sure to define it before the GET route.

  • attachValidation: attach validationError to request, if there is a schema validation error, instead of sending the error to the error handler.

  • onRequest(request, reply, done): a function as soon that a request is received, it could also be an array of functions.

  • preParsing(request, reply, done): a called before parsing the request, it could also be an array of functions.

  • preValidation(request, reply, done): a function called after the shared preValidation hooks, useful if you need to perform authentication at route level for example, it could also be an array of functions.

  • preHandler(request, reply, done): a called just before the request handler, it could also be an array of functions.

  • preSerialization(request, reply, payload, done): a function called just before the serialization, it could also be an array of functions.

  • onSend(request, reply, payload, done): a called right before a response is sent, it could also be an array of functions.

  • onResponse(request, reply, done): a function called when a response has been sent, so you will not be able to send more data to the client. It could also be an array of functions.

  • handler(request, reply): the function that will handle this request. The will be bound to this when the handler is called. Note: using an arrow function will break the binding of this.

  • errorHandler(error, request, reply): a custom error handler for the scope of the request. Overrides the default error global handler, and anything set by setErrorHandler, for requests to the route. To access the default handler, you can access instance.errorHandler. Note that this will point to fastify’s default errorHandler only if a plugin hasn’t overridden it already.

  • validatorCompiler({ schema, method, url, httpPart }): function that builds schemas for request validations. See the documentation.

  • serializerCompiler({ { schema, method, url, httpStatus } }): function that builds schemas for response serialization. See the Validation and Serialization documentation.

  • schemaErrorFormatter(errors, dataVar): function that formats the errors from the validation compiler. See the documentation. Overrides the global schema error formatter handler, and anything set by setSchemaErrorFormatter, for requests to the route.

  • bodyLimit: prevents the default JSON body parser from parsing request bodies larger than this number of bytes. Must be an integer. You may also set this option globally when first creating the Fastify instance with fastify(options). Defaults to 1048576 (1 MiB).

  • logLevel: set log level for this route. See below.

  • logSerializers: set serializers to log for this route.

  • config: object used to store custom configuration.

  • version: a semver compatible string that defined the version of the endpoint. .

    • both (default): Will register both /prefix and /prefix/.
    • slash: Will register only /prefix/.
    • no-slash: Will register only /prefix.

    request is defined in Request.

    reply is defined in .

Notice: The documentation of onRequest, preParsing, preValidation, preHandler, preSerialization, onSend, and onResponse are described in more detail in Hooks. Additionally, to send a response before the request is handled by the handler please refer to .

Example:

  1. fastify.route({
  2.   method: 'GET',
  3.   url: '/',
  4.   schema: {
  5.     querystring: {
  6.       name: { type: 'string' },
  7.       excitement: { type: 'integer' }
  8.     },
  9.     response: {
  10.       200: {
  11.         type: 'object',
  12.         properties: {
  13.           hello: { type: 'string' }
  14.         }
  15.       }
  16.     }
  17.   },
  18.   handler: function (request, reply) {
  19.     reply.send({ hello: 'world' })
  20.   }
  21. })

Shorthand declaration

The above route declaration is more Hapi-like, but if you prefer an Express/Restify approach, we support it as well:
fastify.get(path, [options], handler)
fastify.head(path, [options], handler)
fastify.post(path, [options], handler)
fastify.put(path, [options], handler)
fastify.delete(path, [options], handler)
fastify.options(path, [options], handler)
fastify.patch(path, [options], handler)

Example:

  1. const opts = {
  2.   schema: {
  3.     response: {
  4.       200: {
  5.         type: 'object',
  6.         properties: {
  7.           hello: { type: 'string' }
  8.         }
  9.       }
  10.     }
  11.   }
  12. }
  13. fastify.get('/', opts, (request, reply) => {
  14.   reply.send({ hello: 'world' })
  15. })

fastify.all(path, [options], handler) will add the same handler to all the supported methods.

The handler may also be supplied via the options object:

  1. const opts = {
  2.     response: {
  3.       200: {
  4.         type: 'object',
  5.         properties: {
  6.           hello: { type: 'string' }
  7.         }
  8.       }
  9.     }
  10.   },
  11.   handler: function (request, reply) {
  12.     reply.send({ hello: 'world' })
  13.   }
  14. }
  15. fastify.get('/', opts)

Fastify supports both static and dynamic URLs.
To register a parametric path, use the colon before the parameter name. For wildcard, use the star. Remember that static routes are always checked before parametric and wildcard.

  1. // parametric
  2. fastify.get('/example/:userId', (request, reply) => {})
  3. fastify.get('/example/:userId/:secretToken', (request, reply) => {})
  5. // wildcard
  6. fastify.get('/example/*', (request, reply) => {})

Regular expression routes are supported as well, but pay attention, RegExp are very expensive in term of performance!

  1. // parametric with regexp
  2. fastify.get('/example/:file(^\\d+).png', (request, reply) => {})

It is possible to define more than one parameter within the same couple of slash (“/“). Such as:

  1. fastify.get('/example/near/:lat-:lng/radius/:r', (request, reply) => {})

Remember in this case to use the dash (“-“) as parameters separator.

Finally it is possible to have multiple parameters with RegExp.

  1. fastify.get('/example/at/:hour(^\\d{2})h:minute(^\\d{2})m', (request, reply) => {})

In this case as parameter separator it is possible to use whatever character is not matched by the regular expression.

Having a route with multiple parameters may affect negatively the performance, so prefer single parameter approach whenever possible, especially on routes that are on the hot path of your application. If you are interested in how we handle the routing, check out .

If you want a path containing a colon without declaring a parameter, use a double colon. For example:

Async Await

Are you an async/await user? We have you covered!

  1. fastify.get('/', options, async function (request, reply) {
  2.   var data = await getData()
  3.   var processed = await processData(data)
  4.   return processed
  5. })

As you can see, we are not calling reply.send to send back the data to the user. You just need to return the body and you are done!

If you need it you can also send back the data to the user with reply.send.

  1. fastify.get('/', options, async function (request, reply) {
  2.   var data = await getData()
  3.   var processed = await processData(data)
  4.   reply.send(processed)
  5. })

If the route is wrapping a callback-based API that will call reply.send() outside of the promise chain, it is possible to await reply:

  1. fastify.get('/', options, async function (request, reply) {
  2.   setImmediate(() => {
  3.     reply.send({ hello: 'world' })
  4.   })
  5.   await reply
  6. })

Returning reply also works:

  1. fastify.get('/', options, async function (request, reply) {
  2.   setImmediate(() => {
  3.     reply.send({ hello: 'world' })
  4.   })
  5.   return reply
  6. })
  • When using both return value and reply.send(value) at the same time, the first one that happens takes precedence, the second value will be discarded, and a warn log will also be emitted because you tried to send a response twice.
  • You cannot return undefined. For more details read .

Promise resolution

If your handler is an async function or returns a promise, you should be aware of a special behavior that is necessary to support the callback and promise control-flow. If the handler’s promise is resolved with undefined, it will be ignored causing the request to hang and an error log to be emitted.

  1. If you want to use async/await or promises but return a value with reply.send:
    • Do not return any value.
    • Do not forget to call reply.send.
  2. If you want to use async/await or promises:
    • Do not use reply.send.
    • Do not return undefined.

In this way, we can support both callback-style and async-await, with the minimum trade-off. In spite of so much freedom we highly recommend to go with only one style because error handling should be handled in a consistent way within your application.

Notice: Every async function returns a promise by itself.

Sometimes you need to maintain two or more different versions of the same API; a classic approach is to prefix all the routes with the API version number, /v1/user for example. Fastify offers you a fast and smart way to create different versions of the same API without changing all the route names by hand, route prefixing. Let’s see how it works:

  1. // server.js
  2. const fastify = require('fastify')()
  4. fastify.register(require('./routes/v1/users'), { prefix: '/v1' })
  5. fastify.register(require('./routes/v2/users'), { prefix: '/v2' })
  7. fastify.listen(3000)
  1. // routes/v1/users.js
  2. module.exports = function (fastify, opts, done) {
  3.   fastify.get('/user', handler_v1)
  4.   done()
  5. }
  1. // routes/v2/users.js
  2. module.exports = function (fastify, opts, done) {
  3.   fastify.get('/user', handler_v2)
  4.   done()
  5. }

Fastify will not complain because you are using the same name for two different routes, because at compilation time it will handle the prefix automatically (this also means that the performance will not be affected at all!).

Now your clients will have access to the following routes:

  • /v1/user
  • /v2/user

You can do this as many times as you want, it works also for nested register and routes parameter are supported as well. Be aware that if you use this option will not work.

Handling of / route inside prefixed plugins

The / route has a different behavior depending on if the prefix ends with / or not. As an example, if we consider a prefix /something/, adding a / route will only match /something/. If we consider a prefix /something, adding a / route will match both /something and /something/.

See the prefixTrailingSlash route option above to change this behavior.

Custom Log Level

It could happen that you need different log levels in your routes; Fastify achieves this in a very straightforward way.
You just need to pass the option logLevel to the plugin option or the route option with the value that you need.

Be aware that if you set the logLevel at plugin level, also the and setErrorHandler will be affected.

Or you can directly pass it to a route:

  1. fastify.get('/', { logLevel: 'warn' }, (request, reply) => {
  2.   reply.send({ hello: 'world' })
  3. })

Remember that the custom log level is applied only to the routes, and not to the global Fastify Logger, accessible with fastify.log

Custom Log Serializer

In some context, you may need to log a large object but it could be a waste of resources for some routes. In this case, you can define some serializer and attach them in the right context!

  1. const fastify = require('fastify')({ logger: true })
  3. fastify.register(require('./routes/user'), {
  4.   logSerializers: {
  5.     user: (value) => `My serializer one - ${value.name}`
  6.   }
  7. })
  8. fastify.register(require('./routes/events'), {
  9.   logSerializers: {
  10.     user: (value) => `My serializer two - ${value.name} ${value.surname}`
  11.   }
  12. })
  14. fastify.listen(3000)

You can inherit serializers by context:

  1. const fastify = Fastify({
  2.   logger: {
  3.     level: 'info',
  4.     serializers: {
  5.         return {
  6.           method: req.method,
  7.           url: req.url,
  8.           headers: req.headers,
  9.           hostname: req.hostname,
  10.           remoteAddress: req.ip,
  11.           remotePort: req.socket.remotePort
  12.         }
  13.       }
  14.     }
  15.   }
  16. })
  18. fastify.register(context1, {
  19.   logSerializers: {
  20.     user: value => `My serializer father - ${value}`
  21.   }
  22. })
  24. async function context1 (fastify, opts) {
  25.   fastify.get('/', (req, reply) => {
  26.     req.log.info({ user: 'call father serializer', key: 'another key' })
  27.     // shows: { user: 'My serializer father - call father  serializer', key: 'another key' }
  28.     reply.send({})
  29.   })
  30. }
  32. fastify.listen(3000)

Registering a new handler, you can pass a configuration object to it and retrieve it in the handler.

  1. // server.js
  2. const fastify = require('fastify')()
  4. function handler (req, reply) {
  5.   reply.send(reply.context.config.output)
  6. }
  8. fastify.get('/en', { config: { output: 'hello world!' } }, handler)
  9. fastify.get('/it', { config: { output: 'ciao mondo!' } }, handler)
  11. fastify.listen(3000)

Constraints

Fastify supports constraining routes to match only certain requests based on some property of the request, like the Host header, or any other value via find-my-way constraints. Constraints are specified in the constraints property of the route options. Fastify has two built-in constraints ready for use: the version constraint and the host constraint, and you can add your own custom constraint strategies to inspect other parts of a request to decide if a route should be executed for a request.

Version Constraints

You can provide a version key in the constraints option to a route. Versioned routes allow you to declare multiple handlers for the same HTTP route path, which will then be matched according to each request’s Accept-Version header. The Accept-Version header value should follow the semver specification, and routes should be declared with exact semver versions for matching.
Fastify will require a request Accept-Version header to be set if the route has a version set, and will prefer a versioned route to a non-versioned route for the same path. Advanced version ranges and pre-releases currently are not supported.
Be aware that using this feature will cause a degradation of the overall performances of the router.

  1. fastify.route({
  2.   method: 'GET',
  3.   url: '/',
  4.   constraints: { version: '1.2.0' },
  5.   handler: function (request, reply) {
  6.     reply.send({ hello: 'world' })
  7.   }
  8. })
  10. fastify.inject({
  11.   method: 'GET',
  12.   url: '/',
  13.   headers: {
  14.     'Accept-Version': '1.x' // it could also be '1.2.0' or '1.2.x'
  15.   }
  16. }, (err, res) => {
  17.   // { hello: 'world' }
  18. })

⚠ Security Notice

Remember to set a Vary header in your responses with the value you are using for defining the versioning (e.g.: 'Accept-Version'), to prevent cache poisoning attacks. You can also configure this as part of your Proxy/CDN.

  1. const append = require('vary').append
  2. fastify.addHook('onSend', async (req, reply) => {
  3.   if (req.headers['accept-version']) { // or the custom header you are using
  4.     let value = reply.getHeader('Vary') || ''
  5.     const header = Array.isArray(value) ? value.join(', ') : String(value)
  6.     if ((value = append(header, 'Accept-Version'))) { // or the custom header you are using
  7.       reply.header('Vary', value)
  8.     }
  9.   }
  10. })

If you declare multiple versions with the same major or minor, Fastify will always choose the highest compatible with the Accept-Version header value.
If the request will not have the Accept-Version header, a 404 error will be returned.

It is possible to define a custom version matching logic. This can be done through the configuration when creating a Fastify server instance.

Host Constraints

You can provide a host key in the constraints route option for to limit that route to only be matched for certain values of the request Host header. host constraint values can be specified as strings for exact matches or RegExps for arbitrary host matching.

  1. fastify.route({
  2.   method: 'GET',
  3.   url: '/',
  4.   constraints: { host: 'auth.fastify.io' },
  5.   handler: function (request, reply) {
  6.     reply.send('hello world from auth.fastify.io')
  7.   }
  8. })
  10. fastify.inject({
  11.   method: 'GET',
  12.   url: '/',
  13.   headers: {
  14.     'Host': 'example.com'
  15.   }
  16. }, (err, res) => {
  17.   // 404 because the host doesn't match the constraint
  18. })
  20. fastify.inject({
  21.   method: 'GET',
  22.   url: '/',
  23.   headers: {
  24.     'Host': 'auth.fastify.io'
  25.   }
  26. }, (err, res) => {
  27.   // => 'hello world from auth.fastify.io'