Apiv

A Hapi.js plugin that automatically adds version prefixes to all your API routes, making it easy to version your API endpoints.

Installation

npm install apiv

Features

• Automatically prefixes all routes with a version and/or API prefix
• Global configuration applies to all routes
• Simple setup with sensible defaults
• Supports custom prefixes and version strings
• Can be disabled globally when needed
• TypeScript support included

Usage

Basic Example

By default, the plugin prefixes all routes with /api/v1:

import Hapi from '@hapi/hapi'
import Apiv from 'apiv'

const server = Hapi.server({ port: 3000 })

await server.register({ plugin: Apiv })

server.route({
  method: 'GET',
  path: '/users',
  handler: () => ({ users: [] })
})

await server.start()
// Route is now accessible at: GET /api/v1/users

Custom Version and Prefix

You can customize both the version and prefix:

await server.register({
  plugin: Apiv,
  options: {
    version: 'v2',
    prefix: 'service'
  }
})

server.route({
  method: 'GET',
  path: '/users',
  handler: () => ({ users: [] })
})
// Route is now accessible at: GET /service/v2/users

Empty Prefix or Version

You can set either option to an empty string to exclude it:

// Only version, no prefix
await server.register({
  plugin: Apiv,
  options: {
    prefix: '',
    version: 'v1'
  }
})
// Routes accessible at: GET /v1/users

// Only prefix, no version
await server.register({
  plugin: Apiv,
  options: {
    prefix: 'api',
    version: ''
  }
})
// Routes accessible at: GET /api/users

// Neither (routes unchanged)
await server.register({
  plugin: Apiv,
  options: {
    prefix: '',
    version: ''
  }
})
// Routes accessible at: GET /users

Disabling the Plugin

You can disable the plugin entirely by setting enabled: false:

await server.register({
  plugin: Apiv,
  options: { enabled: false }
})

server.route({
  method: 'GET',
  path: '/users',
  handler: () => ({ users: [] })
})
// Route remains at: GET /users (no prefix applied)

Configuration

Global Options

All configuration is done at the plugin registration level:

Option	Type	Default	Description
version	string	'v1'	Version string to prepend to routes (max 255 chars)
prefix	string	'api'	Prefix string to prepend before version (max 255 chars)
enabled	boolean	true	Whether to enable the plugin

Important Notes

• Per-Route Overrides Supported (via aliases): Add options.plugins.apiv to a route to create an extra alias path with a different prefix and/or version. The global path still exists.
• Global Prefix Remains: The plugin sets a global prefix for all routes; per-route overrides add aliases and do not replace the global path.
• Per-Route Disable (alias): Use options.plugins.apiv: false or { enabled: false } to add an unprefixed alias for that route. The globally prefixed path remains unless the plugin is disabled globally.
• Route Settings Fully Preserved: Alias routes copy all route configuration from the original route — including auth, validate, cors, payload, pre, tags, and all other options. The alias route id is not copied to avoid conflicts.
• Registration Order Matters: Apiv must be registered in a separate await server.register() call that completes before any plugin that registers routes. See Registration Order below.

Registration Order

Apiv works by setting a prefix on the root Hapi realm at registration time. Hapi propagates realm prefixes to child plugins at the start of each server.register() call, before any plugin in that call has run. This means that if Apiv and your route plugins are passed to the same server.register() call, the route plugins will not inherit the prefix — and routes will not be versioned.

Correct: separate register calls

// Apiv runs first and sets the realm prefix
await server.register({ plugin: Apiv })

// Route plugins now inherit the prefix correctly
await server.register([
  routerPlugin,
  otherPlugin
])
// Routes are accessible at: GET /api/v1/users, etc.

Incorrect: same register call

// Apiv and the router are in the same call — routes will NOT be versioned
await server.register([
  { plugin: Apiv },
  routerPlugin       // ← routes registered here won't get the prefix
])

If Apiv and route plugins must share a single server.register() call for some reason, routes will remain at their plain paths (e.g. /health instead of /api/v1/health). Any options.plugins.apiv overrides on those routes are silently skipped — no conflict or error is thrown.

Route-Level Overrides

You can add route-specific overrides using options.plugins.apiv. These do not modify the original route registration; they create additional alias paths at server startup.

Version Override

server.route({
  method: 'GET',
  path: '/users',
  options: { plugins: { apiv: { version: 'v2' } } },
  handler: () => ({ users: [] })
})
// Aliases:
// - Global:   GET /api/v1/users
// - Override: GET /api/v2/users

Prefix Override

server.route({
  method: 'GET',
  path: '/users',
  options: { plugins: { apiv: { prefix: 'service' } } },
  handler: () => ({ users: [] })
})
// Aliases:
// - Global:   GET /api/v1/users
// - Override: GET /service/v1/users

Prefix + Version Override

server.route({
  method: 'GET',
  path: '/users',
  options: { plugins: { apiv: { prefix: 'service', version: 'v3' } } },
  handler: () => ({ users: [] })
})
// Aliases:
// - Global:   GET /api/v1/users
// - Override: GET /service/v3/users

Empty Version Override

server.route({
  method: 'GET',
  path: '/users',
  options: { plugins: { apiv: { version: '' } } },
  handler: () => ({ users: [] })
})
// Aliases:
// - Global:   GET /api/v1/users
// - Override: GET /api/users

Per-Route Disable

// Disable via boolean
server.route({
  method: 'GET',
  path: '/health',
  options: { plugins: { apiv: false } },
  handler: () => ({ status: 'ok' })
})

// Disable via object
server.route({
  method: 'GET',
  path: '/status',
  options: { plugins: { apiv: { enabled: false } } },
  handler: () => ({ status: 'ok' })
})

// Aliases:
// - Global:     GET /api/v1/health, /api/v1/status
// - Unprefixed: GET /health, /status

Route Options Preservation

Alias routes created by per-route overrides or disabling copy the complete route configuration from the original route. Settings such as:

• auth — authentication requirements
• validate — request validation schemas
• cors — CORS settings
• payload — payload parsing options
• pre — prerequisite handlers
• timeout, description, notes, tags — and all other options

...are applied to both the original prefixed route and any alias routes. The only exception is the route id, which is not copied to avoid duplicate ID conflicts.

Example

server.route({
  method: 'GET',
  path: '/secure',
  options: {
    auth: 'jwt',
    validate: {
      query: Joi.object({
        id: Joi.string().required()
      })
    },
    plugins: { apiv: false }  // Creates alias at /secure
  },
  handler: () => ({ data: 'sensitive' })
})

// Result:
// - GET /api/v1/secure - Has auth and validation
// - GET /secure        - Also has auth and validation

Examples

Multiple Versions on Same Server

If you need to support multiple API versions, you can register separate server instances or use different plugins:

// All routes get v1 prefix
await server.register({
  plugin: Apiv,
  options: { version: 'v1' }
})

server.route({
  method: 'GET',
  path: '/users',
  handler: () => ({ version: 1 })
})
// Accessible at: GET /api/v1/users

Nested Paths

The plugin works with any route path structure:

server.route({
  method: 'GET',
  path: '/users/{id}/posts',
  handler: () => ({ posts: [] })
})
// Accessible at: GET /api/v1/users/{id}/posts

Root Path

Even the root path gets prefixed:

server.route({
  method: 'GET',
  path: '/',
  handler: () => ({ message: 'API Root' })
})
// Accessible at: GET /api/v1

TypeScript

The plugin includes TypeScript definitions:

import { Server } from '@hapi/hapi'
import Apiv, { ApiVersionPluginOptions } from 'apiv'

const server: Server = Hapi.server({ port: 3000 })

const options: ApiVersionPluginOptions = {
  version: 'v2',
  prefix: 'api',
  enabled: true
}

await server.register({ plugin: Apiv, options })

License

MIT