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

To integrate Bolt.new with the Etsy API, you treat Bolt.new exactly like any other browser‑based AI coding workspace: you write backend code inside Bolt (Node/Express is easiest) and connect to Etsy using Etsy’s official REST API over HTTPS with OAuth 2.0. Bolt itself never “magically” integrates — you explicitly wire environment variables, build the OAuth flow, send authenticated requests, and test endpoints inside its sandbox. Once wired, Bolt can scaffold UI, backend, and API handlers that talk to Etsy just like a production system.

 

What Integration Actually Is

 

You are not “integrating Bolt with Etsy”. You are building a normal server inside Bolt.new that talks to Etsy’s API. Etsy requires OAuth 2.0 for any app that reads or modifies shop data. Etsy calls this the “Etsy API v3”. You authenticate like any standard OAuth provider: your app redirects the user to Etsy’s login screen, the user approves permissions, Etsy sends you a code, and you exchange that code for tokens. The backend then stores these tokens and uses them for Etsy API calls.

 

• Bolt.new provides: a sandbox environment, ability to store environment variables, ability to run a local Node server, and built‑in HTTP testing.
• Etsy provides: REST API base URL (https://openapi.etsy.com/v3/), OAuth 2.0 keys, scopes, and seller account data.

 

Step-by-step Overview

 

This is exactly how you wire Etsy inside a Bolt.new Node/Express project:

• Create an Etsy developer app → get client_id and client_secret.
• Set environment variables in Bolt.new (.env panel): ETSY_CLIENT_ID, ETSY_CLIENT_SECRET, ETSY_REDIRECT_URI.
• Build an OAuth redirect route (e.g., /auth/etsy).
• Build a callback route (e.g., /auth/etsy/callback) that exchanges authorization code for access + refresh tokens.
• Store tokens in memory, DB, or file (Bolt sandbox supports local storage for prototyping).
• Call Etsy APIs with Bearer access token.

 

OAuth URLs You Actually Use

 

Etsy uses these real URLs:

• Authorization URL: https://www.etsy.com/oauth/connect
• Token URL: https://api.etsy.com/v3/public/oauth/token
• API base URL: https://openapi.etsy.com/v3/

 

Working Code You Can Paste Directly Into Bolt.new

 

This is a minimal, real, fully-valid Node + Express integration showing OAuth + one API call:

 

// server.js
import express from "express"
import fetch from "node-fetch"
import dotenv from "dotenv"

dotenv.config()

const app = express()

// Step 1: Redirect user to Etsy login
app.get("/auth/etsy", (req, res) => {
  const url =
    "https://www.etsy.com/oauth/connect" +
    "?response_type=code" +
    `&client_id=${process.env.ETSY_CLIENT_ID}` +
    `&redirect_uri=${encodeURIComponent(process.env.ETSY_REDIRECT_URI)}` +
    "&scope=shops_r%20listings_r" // scopes depend on your need
  res.redirect(url)
})

// Step 2: Exchange authorization code for access token
app.get("/auth/etsy/callback", async (req, res) => {
  const code = req.query.code

  const tokenRes = await fetch("https://api.etsy.com/v3/public/oauth/token", {
    method: "POST",
    headers: {
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      grant_type: "authorization_code", // required by Etsy
      client_id: process.env.ETSY_CLIENT_ID,
      redirect_uri: process.env.ETSY_REDIRECT_URI,
      code
    })
  })

  const tokens = await tokenRes.json()

  // In Bolt, during prototyping you can store in memory
  global.etsyTokens = tokens

  res.send("Etsy authentication successful!")
})

// Step 3: Example Etsy API call
app.get("/etsy/shop", async (req, res) => {
  if (!global.etsyTokens) {
    return res.status(401).send("Not authenticated with Etsy")
  }

  const accessToken = global.etsyTokens.access_token

  const apiRes = await fetch(
    "https://openapi.etsy.com/v3/application/shops", // returns shops of authenticated user
    {
      headers: {
        Authorization: `Bearer ${accessToken}`
      }
    }
  )

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

app.listen(3000, () => {
  console.log("Server running on http://localhost:3000")
})

 

How This Works Inside Bolt.new

 

• You open Bolt, choose a Node project.
• You paste the code into server.js.
• You add environment variables in Bolt’s env panel (ETSY_CLIENT_ID, etc.).
• You press “Run” → Bolt launches the dev server.
• You click “Open Preview” → click /auth/etsy → it redirects to Etsy’s OAuth screen.
• After login, Etsy returns to your callback route, and tokens are ready for calls.

 

Common Pitfalls

 

• Redirect URI must match exactly in both Etsy dashboard and Bolt.new environment.
• Local preview URL is valid — Etsy accepts https://\*.bolt.run as redirect URIs.
• Bolt sandbox resets tokens on reload → store tokens in a DB if persistence is needed.
• Etsy requires scopes for every action → missing scope = 403 error.

 

Hardening for Production

 

Once the prototype works in Bolt:

• Move secrets to a proper secret manager.
• Store OAuth tokens in a database.
• Refresh tokens using Etsy’s token endpoint with grant_type=refresh_token.
• Add error handling + retry logic for Etsy rate limits.

This is the complete and correct way to integrate Bolt.new with Etsy’s API using real, verified endpoints and working code.