Natively Pronounced Mandarin

    TypeScript icon, indicating that this package has built-in type declarations

    0.1.4 • Public • Published

    npm (scoped) npm GitHub Workflow Status

    @apideck/reva 🕵

    Validate requests based on OpenAPI

    • Supports all OpenAPI parameters
    • Based on AJV
    • Readable and helpful errors (by @apideck/better-ajv-errors)
    • High quality TypeScript definitions included
    • Minimal footprint: 42 kB including AJV (gzip + minified)


    $ yarn add @apideck/reva


    $ npm i @apideck/reva


    Create a Reva instance and call the validate method with your OpenAPI operation and your request data.

    import { Reva } from '@apideck/reva';
    const reva = new Reva();
    const result = reva.validate({
      operation, // OpenAPI operation
      request: {
        headers: { 'X-My-Header': 'value', Cookie: 'Key=Value' },
        pathParameters; { id: 'ed55e7a3' },
        queryParameters; { search: 'foo' },
        body: {},
    if (result.ok) {
      // Valid request!
    } else {
      // Invalid request, result.errors contains validation errors



    Reva is the main Request validation class. You can optionally pass options to the constructor.

    new Reva(options?: RevaOptions)


    • options: RevaOptions
      • allowAdditionalParameters?: true | OpenApiParameterType[] Allow additional parameters to be passed that are not defined in the OpenAPI operation. Use true to allow all parameter types to have additional parameters. Default value: ['header', 'cookie']
      • partialBody?: boolean Ignore required properties on the requestBody. This option is useful for update endpoints where a subset of required properties is allowed. Default value: false
      • groupedParameters?: OpenApiParameterType[] Validate multiple OpenAPI parameter types as one schema. This is useful for APIs where parameters (query,path, etc) are combined into a single parameters object. Default value: []

    reva.validate(options: RevaValidateOptions)

    Validate requests based on OpenAPI. Parameter validation uses type coercion, request body validation does not. When a Content-Type header is passed, it has to match a Content-Type defined in the OpenAPI operation. Default Content-Type is application/json.


    • options: RevaValidateOptions
      • operation: OpenApiOperation Your OpenAPI operation object to validate against
      • request: RevaRequest The request data to validate. All properties are optional
        • queryParameters?: Record<string, unknown> Query parameters to validate
        • headers?: Record<string, unknown> Headers to validate
        • pathParameters?: Record<string, unknown> Path parameters to validate
        • body?: unknown Request body to validate
      • options?: RevaOptions Override options set in the Reva constructor

    Return Value

    • Result<ValidationError>
      • ok: boolean Indicates if the request is valid or not
      • errors?: ValidationError[] Array of formatted errors. Only populated when Result.ok is false
        • message: string Formatted error message
        • suggestion?: string Optional suggestion based on provided data and schema
        • path: string Object path where the error occurred (example:
        • context: { errorType: DefinedError['keyword']; [additionalContext: string]: unknown } errorType is error.keyword proxied from ajv. errorType can be used as a key for i18n if needed. There might be additional properties on context, based on the type of error.


    npm i @apideck/reva

    DownloadsWeekly Downloads






    Unpacked Size

    105 kB

    Total Files


    Last publish


    • brahimmouhamou
    • gdewilde
    • geertwille
    • jakeprins
    • nicklloyd
    • eliasmeire
    • trinix