Bolt.new AI and Pinterest Ads integration: Step-by-Step Guide 2025

To integrate Bolt.new AI with Pinterest Ads, you don’t connect “Bolt” to Pinterest directly. Instead, you build a normal full‑stack API integration inside your Bolt.new project using Pinterest’s real Ads API. Bolt is simply the workspace where you scaffold UI, routes, server code, and secure environment variables. Pinterest Ads uses a standard OAuth2 flow, REST endpoints, and Bearer tokens — so integration is absolutely possible as long as you follow Pinterest’s official API specs.

 

What the integration actually is

 

You’ll build a backend route (Node or Python) inside Bolt.new that:

• Redirects the user to Pinterest OAuth login.
• Receives the OAuth authorization code in a callback.
• Exchanges that code for an access token.
• Uses that token to call Pinterest Ads API endpoints (create ads, pull metrics, manage campaigns, etc.).
• Stores tokens in environment variables or your own DB (outside Bolt for production).

Bolt.new doesn’t provide a Pinterest plugin — you wire it yourself using APIs. Pinterest Ads API is fully documented and stable; it uses regular HTTPS JSON requests, so integration is straightforward.

 

Steps to Integrate Pinterest Ads inside Bolt.new

 

These steps work in any Bolt.new workspace running a backend (Node.js example below). The same structure works in Python if you prefer.

• Create Pinterest app at https://developers.pinterest.com → you get Client ID, Client Secret, and set your OAuth redirect URL (e.g. https://your-bolt-app.bolt.run/api/pinterest/callback).
• Add environment variables in Bolt:
  PINTEREST_CLIENT_ID
  PINTEREST_CLIENT_SECRET
  PINTEREST_REDIRECT_URI
• Implement OAuth redirect route to send user to Pinterest login.
• Implement OAuth callback route to exchange “code” for “access token”.
• Call Pinterest Ads API with the token using standard REST calls.

 

Working Node.js Example (real Pinterest API patterns)

 

// routes/pinterest.js
import express from "express";
import fetch from "node-fetch"; // Works in Bolt.new Node runtime

const router = express.Router();

// Step 1 → Send user to Pinterest OAuth
router.get("/auth", (req, res) => {
  const params = new URLSearchParams({
    response_type: "code",
    client_id: process.env.PINTEREST_CLIENT_ID,
    redirect_uri: process.env.PINTEREST_REDIRECT_URI,
    scope: "ads:read ads:write" // adjust scopes as needed
  });

  res.redirect(`https://www.pinterest.com/oauth/?${params.toString()}`);
});

// Step 2 → Receive authorization code + exchange token
router.get("/callback", async (req, res) => {
  const { code } = req.query;

  const tokenRes = await fetch("https://api.pinterest.com/v5/oauth/token", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      grant_type: "authorization_code",
      code: code,
      redirect_uri: process.env.PINTEREST_REDIRECT_URI,
      client_id: process.env.PINTEREST_CLIENT_ID,
      client_secret: process.env.PINTEREST_CLIENT_SECRET
    })
  });

  const tokenData = await tokenRes.json();

  // tokenData.access_token is the usable Ads API token
  // In production save this to DB; in Bolt store temporarily in memory or env
  
  global.pinterestToken = tokenData.access_token;

  res.send("Pinterest Auth Complete. Token stored.");
});

// Step 3 → Example API call: get advertiser accounts
router.get("/ads/accounts", async (req, res) => {
  if (!global.pinterestToken) {
    return res.status(401).send("Pinterest not authenticated yet.");
  }

  const apiRes = await fetch("https://api.pinterest.com/v5/ad_accounts", {
    headers: {
      Authorization: `Bearer ${global.pinterestToken}`
    }
  });

  const data = await apiRes.json();
  res.json(data);
});

export default router;

 

How to wire in Bolt.new

 

• Create a routes directory and save the above file.
• Import the router into your main Express file (e.g. server.js).
• Set environment variables via Bolt.new environment panel.
• Run the project in Bolt preview → test endpoints with OAuth flow.
• Use frontend code to call your backend:
  /api/pinterest/auth → user logs in
  /api/pinterest/ads/accounts → fetch ad accounts

 

Important Practical Points

 

• Bolt.new does NOT store secrets permanently. For production you must store tokens in your real backend/database.
• Pinterest requires HTTPS redirect URIs. Bolt’s preview URLs are HTTPS, so this works.
• Pinterest Ads API is rate-limited; test politely.
• Production hardening: move token storage to a real DB, add token refresh handling, and restrict scopes.

 

Summary

 

Integrating Bolt.new with Pinterest Ads simply means: use Bolt as the environment to build a standard Pinterest Ads API integration. You perform OAuth, store tokens, and make REST requests from your backend routes. The example code above is real, uses Pinterest’s actual API flow, and can run directly inside a Bolt.new full‑stack project.