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

You don’t “integrate Bolt.new AI with Sendible” directly, because Bolt.new is not a social‑media tool and Sendible does not offer any built‑in AI‑assistant connectors. What you actually do is integrate your Bolt.new‑built app (front‑end + server code running inside the Bolt sandbox) with Sendible’s REST API. The API is real, documented, and requires OAuth2. Once you authenticate, your Bolt app can create posts, schedule posts, fetch analytics, etc., exactly the same way any backend service would.

 

What the integration really means

 

You’ll build a small backend inside Bolt.new (Node.js server file) that holds your Sendible credentials, completes OAuth2, and calls Sendible’s API endpoints. Then your Bolt UI (React or plain JS) uses that backend to trigger actions like “schedule a post”. Bolt itself is just the workspace — nothing special or hidden happens.

• Your Bolt server talks to Sendible using HTTPS + OAuth2 headers.
• Your Bolt client talks to your Bolt server using normal fetch requests.
• All secrets stay on the server side inside environment variables.

 

Step‑by‑step: How to integrate

 

Below is the exact pattern used in the real world with Sendible’s API.

• Create a Sendible app in your Sendible dashboard → this gives you a Client ID, Client Secret, and a Redirect URI.
• Add environment variables in Bolt.new:
  • SENDIBLE_CLIENT_ID
  • SENDIBLE_CLIENT_SECRET
  • SENDIBLE_REDIRECT_URI
• Implement the OAuth2 authorization URL so a user can click “Connect to Sendible” from your UI.
• Create a backend route to handle Sendible’s redirect, exchange the authorization code for an access token, and store that token (usually session, DB, or temporary in‑memory store in Bolt for prototypes).
• Call Sendible’s REST endpoints using Bearer tokens.

 

Real working code (Node.js backend inside bolt.new)

 

import express from "express";
import fetch from "node-fetch";

const app = express();

// OAuth redirect to Sendible
app.get("/auth/sendible", (req, res) => {
  const authUrl =
    "https://app.sendible.com/api/v2/oauth/authorize" +
    `?client_id=${process.env.SENDIBLE_CLIENT_ID}` +
    `&redirect_uri=${encodeURIComponent(process.env.SENDIBLE_REDIRECT_URI)}` +
    `&response_type=code`;

  res.redirect(authUrl);
});

// Sendible callback → exchange code for access token
app.get("/auth/sendible/callback", async (req, res) => {
  const code = req.query.code;

  const tokenRes = await fetch("https://app.sendible.com/api/v2/oauth/token", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      client_id: process.env.SENDIBLE_CLIENT_ID,
      client_secret: process.env.SENDIBLE_CLIENT_SECRET,
      redirect_uri: process.env.SENDIBLE_REDIRECT_URI,
      grant_type: "authorization_code",
      code
    })
  });

  const tokenData = await tokenRes.json();

  // Store securely (DB or session). In Bolt prototype: memory.
  req.session.sendibleToken = tokenData.access_token;

  res.send("Sendible connected successfully");
});

// Example: schedule a social post through Sendible
app.post("/sendible/post", express.json(), async (req, res) => {
  const token = req.session.sendibleToken;
  if (!token) return res.status(401).send("Not authenticated with Sendible");

  const result = await fetch("https://app.sendible.com/api/v2/posts", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${token}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      message: req.body.message,
      profile_ids: req.body.profileIds, // real Sendible field
      send_at: req.body.sendAt
    })
  });

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

export default app;

 

How the frontend in Bolt.new calls this

 

// Example React action in Bolt.new
async function sendPost() {
  const res = await fetch("/sendible/post", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      message: "Hello from Bolt + Sendible!",
      profileIds: [123456], // must be real IDs from Sendible
      sendAt: null // post immediately
    })
  });

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

 

Important realities & limits

 

• Bolt does not store tokens long‑term. For real deployments, move the backend to a real server and store tokens in a database.
• Sendible’s API rate limits apply. Avoid making high‑frequency calls from the frontend.
• OAuth requires HTTPS. Bolt.new preview URLs work fine for prototyping, but production requires a proper domain.
• You must register the exact redirect URI in Sendible; mismatches cause OAuth errors.

 

The full mental model

 

Bolt.new is your development environment. Sendible is a third‑party social scheduling API. You integrate them exactly like any other SaaS: OAuth → store token → call REST endpoints. No hidden AI glue, no proprietary connection layer, just standard HTTP APIs and auth.