TrustComponent
NestJS
TrustCaptcha · Bot protection

NestJS CAPTCHA Integration

Add a NestJS CAPTCHA to a controller or guard in a few lines of TypeScript. It stops bot spam on logins, sign-ups and contact forms and fits Nest's dependency injection, ConfigModule and typed DTOs. EU-hosted, GDPR-compliant, no image puzzles.

Quickstart

How the integration works

1. Create a CAPTCHA

Create a user account or log in with an existing one. Then create a new CAPTCHA or pick an existing one. If you want to try TrustCaptcha first, every plan comes with a 14-day free trial.

The CAPTCHA overview page shows your site key and license key, and you create your API key there. Add your website’s domains to the authorized domains in the CAPTCHA security rules so they can use your CAPTCHA.

Start of the CAPTCHA creation form.
CAPTCHA security rules of a demo CAPTCHA.

2. Add the CAPTCHA widget to your form

Drop the TrustCaptcha widget into the HTML form your NestJS controller serves. The widget runs the CAPTCHA in the background and adds a hidden tc-verification-token field on submit, which arrives on req.body like any other input.

contact.html
HTML
<script type="module" src="https://cdn.trustcomponent.com/trustcaptcha/3.0.x/trustcaptcha.esm.min.js"></script>

<form method="post" action="/contact">
    <input type="email" name="email" required>
    <trustcaptcha-component sitekey="<your_site_key>"></trustcaptcha-component>
    <button type="submit">Send</button>
</form>

The CAPTCHA widget will then be displayed inside your form:

CAPTCHA start

Need detailed information about the CAPTCHA widget integration?
Our documentation has the full widget reference, including themes, languages and custom design.

Read the documentation

3. Validate the token in your NestJS controller

In your NestJS controller, take the verification token from the request body, look up the result via our Node.js library, and decide whether to accept the request.

First, install our TrustCaptcha Node.js library:

Install
bash
npm i @trustcomponent/trustcaptcha-nodejs

Then validate the token inside your NestJS controller and act on the result:

contact.controller.ts
TypeScript
import { BadRequestException, Body, Controller, Post } from "@nestjs/common";
import { TrustCaptcha } from "@trustcomponent/trustcaptcha-nodejs";

@Controller("contact")
export class ContactController {
  @Post()
  async submit(@Body() body: { "tc-verification-token": string }) {
    const token = body["tc-verification-token"] ?? "";

    try {
      const result = await TrustCaptcha.getVerificationResult("<your_api_key>", token);
      if (!result.verificationPassed || result.score > 0.5) {
        throw new BadRequestException("CAPTCHA verification failed.");
      }
    } catch {
      throw new BadRequestException("CAPTCHA verification failed.");
    }

    // CAPTCHA passed — process the request
    return { status: "ok" };
  }
}

Need detailed information about the NestJS CAPTCHA integration?
For full step-by-step instructions, including a reusable Guard refactor for projects with several protected endpoints, please read our documentation.

Read the documentation

Other backend framework instead of NestJS?
If you use a different framework, pick the matching recipe here. If your framework isn’t listed, your software developers can integrate the verification themselves using our documentation or ask our support team for a pre-built integration.

Actix Web
ASP.NET Core
Axum
Django
Echo
Express
FastAPI
Fastify
Fiber
Flask
Gin
Hapi
Laravel
Micronaut
NestJS
Next.js
Quarkus
Ruby on Rails
Sinatra
Spring Boot
Symfony

4. Test your integration

TrustCaptcha is now active. Send a test request and check that it goes through.

CAPTCHA done

FAQs

Where does the NestJS CAPTCHA verification go?
Inside the controller method that receives the form submission or, for a cleaner setup with several protected endpoints, inside a custom NestJS guard. Both have access to the request body, where the CAPTCHA token (default name: "tc-verification-token") arrives like any other field.
Should I use a guard, an interceptor or just call the verification in the controller?
For a single endpoint, calling it directly in the controller is fine. For multiple protected endpoints, a guard (TrustCaptchaGuard) is the most idiomatic NestJS pattern: a single @UseGuards(TrustCaptchaGuard) decorator opts any controller method into CAPTCHA verification.
How do I share the API key across the app?
Use Nest's ConfigModule. Inject ConfigService into the guard or controller and read the API key with config.getOrThrow<string>("TRUSTCAPTCHA_API_KEY"). The key itself lives in your .env file or your hosting provider's secret store.
Does NestJS' ValidationPipe interfere with the CAPTCHA token?
No. ValidationPipe only validates DTO fields you've declared. The CAPTCHA token is read from req.body in the guard (or from a typed DTO with a custom decorator), so it works alongside ValidationPipe without any changes.
Do I need to configure body parsing manually?
No. Nest enables express.json() and express.urlencoded() by default, so req.body is parsed before the guard or controller runs and the CAPTCHA token is available out of the box.
Losing leads to CAPTCHAs?

TrustCaptcha blocks spam and bots, not customers. No puzzles, GDPR-compliant, EU-hosted.

CAPTCHA start
CAPTCHA done
No puzzles for visitors
The check runs in the background while visitors type, so more people finish your forms instead of giving up.
GDPR-compliant
Hosted in the EU, no cookies, encrypted transmission and automatic data deletion. Every customer gets a Data Processing Agreement.
Multi-layer security
Adaptive proof-of-work and risk scoring stop abuse early, even when attack traffic spikes.
Full control
Set the sensitivity, keep allow and block lists and use geoblocking. You decide how strict the check is.

Protect your NestJS application with TrustCaptcha in just a few steps!

  • EU-hosted & GDPR-compliant
  • No puzzles
  • Try free for 14 days