Bolt.new AI and Nexmo (Vonage API) integration: Step-by-Step Guide 2025

To integrate Bolt.new with Nexmo (Vonage API), you don’t “connect Bolt to Vonage” directly. Instead, inside a Bolt.new workspace you write backend code (Node.js or Python) that talks to Vonage using its official REST API or SDK, pass your Vonage API credentials via environment variables, and then expose simple functions or API routes that your Bolt-generated frontend or agents can call. In short: Bolt runs your code, your code talks to Vonage. Nothing magical — just standard HTTP requests with proper keys.

 

How Integration Works (The direct answer)

 

You integrate Bolt.new with Nexmo (Vonage) by installing the official Vonage SDK inside the Bolt workspace, creating environment variables for the API Key/Secret (or JWT private key for newer APIs), and writing backend routes that send SMS, verify phone numbers, or trigger voice calls. Bolt itself does not provide any built‑in Vonage connector — you integrate using normal backend code and keep secrets in the Bolt environment settings.

 

What You Actually Do (Step‑by‑step, practical, real)

 

Here’s the real-world pattern, kept simple and valid:

• You create a backend file inside Bolt.new (for example: api/send-sms.js).
• You install Vonage’s official Node.js SDK or use direct REST calls.
• You add environment variables in Bolt: VONAGE_API_KEY, VONAGE_API_SECRET.
• You write a small serverless-style function or Express handler that sends SMS or initiates a voice event via Vonage.
• Your Bolt-generated UI or agent simply calls this backend route.

 

Adding Credentials in Bolt.new

 

In the Bolt editor UI, go to environment variables and add:

• VONAGE_API_KEY
• VONAGE_API_SECRET

You never hardcode credentials in the code.

 

Install Vonage SDK in Bolt

 

npm install @vonage/server-sdk

 

Simple Working Node.js Example (Bolt backend route)

 

// File: api/send-sms.js
// Bolt will treat this as an API endpoint depending on your scaffold.
// This example uses Vonage's Node SDK to send an SMS.

import { Vonage } from '@vonage/server-sdk';

export default async function handler(req, res) {
  try {
    const { to, text } = req.body;

    const vonage = new Vonage({
      apiKey: process.env.VONAGE_API_KEY,        // stored in Bolt env vars
      apiSecret: process.env.VONAGE_API_SECRET   // never commit secrets
    });

    const from = "BoltDemo"; // must be allowed in your Vonage dashboard

    const response = await vonage.sms.send({ to, from, text });

    res.status(200).json({ success: true, response });
  } catch (err) {
    res.status(500).json({ success: false, error: err.message });
  }
}

 

This is real, valid Vonage SDK code. When you deploy and call /api/send-sms, it triggers an SMS.

 

If You Prefer Pure REST Instead of SDK

 

// File: api/send-sms-rest.js
// Calls Vonage SMS REST API directly using fetch.

export default async function handler(req, res) {
  try {
    const { to, text } = req.body;

    const url = "https://rest.nexmo.com/sms/json";

    const params = new URLSearchParams({
      api_key: process.env.VONAGE_API_KEY,
      api_secret: process.env.VONAGE_API_SECRET,
      to,
      from: "BoltDemo",
      text
    });

    const response = await fetch(url, {
      method: "POST",
      headers: { "Content-Type": "application/x-www-form-urlencoded" },
      body: params.toString()
    });

    const data = await response.json();
    res.status(200).json({ success: true, data });
  } catch (e) {
    res.status(500).json({ success: false, error: e.message });
  }
}

 

Triggering SMS from the Bolt Frontend

 

Your frontend simply calls the backend route:

async function sendSMS() {
  const result = await fetch("/api/send-sms", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      to: "+1234567890",
      text: "Hello from Bolt + Vonage!"
    })
  });

  const data = await result.json();
  console.log(data);
}

 

Important Operational Notes

 

• Vonage requires verified phone numbers depending on region and product.
• SMS Sender IDs may be restricted (some countries require specific formats).
• Bolt.new cannot store files privately for JWT private keys unless you embed them securely through environment variables or upload them into the workspace carefully.
• Vonage also supports Voice, Verify, and Messages APIs — all still work the same way: call the REST API or SDK from backend code in Bolt.

The essence: Bolt hosts your backend code; your backend talks to Vonage using standard HTTP/SDK calls with environment-variable credentials. That’s the full, real integration.