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

You integrate Bolt.new with Freightos the same way you integrate any external system in a browser‑based AI workspace: by calling Freightos’ real public REST APIs from your Bolt.new backend code, using an API key stored as an environment variable. There is no native “Bolt–Freightos connector.” You write a standard HTTP client, authenticate with Freightos’ token, call their endpoints (quoting, booking, tracking, etc.), then expose routes or UI in your Bolt project to use them. Everything depends on Freightos’ public API documentation and the API key they issue you.

 

What Integration Really Means

 

Freightos provides a standard REST API. Bolt.new runs normal backend code (Node.js) where you can send HTTPS requests to external APIs. So you integrate by:

• Getting a Freightos API key from their developer portal or dashboard.
• Saving it in Bolt.new as an environment variable (required to keep secrets secure).
• Writing server-side request logic in Bolt (Node.js) to hit Freightos endpoints.
• Building frontend components that call your backend routes.

This is exactly how you'd integrate Stripe, Twilio, or any real external API.

 

What You Need From Freightos

 

Freightos’ API provides operations like: requesting quotes, getting shipping options, checking rates, tracking shipments, etc. They provide:

• API Key for authentication
• Base URL such as https://api.freightos.com (actual path depends on the specific API product)
• Endpoints for quotes, shipments, tracking

You must follow their exact documentation for endpoint paths and fields. Do not guess — Freightos enforces strict schemas.

 

Storing Your API Key in Bolt.new

 

In the Bolt.new environment panel, create an environment variable:

• FREIGHTOS_API_KEY = your-real-api-key-here

This keeps the key out of your code and prevents leaking it in the frontend.

 

Basic Backend Request Example (Node.js inside Bolt.new)

 

// Example backend route in Bolt.new using Express-style handlers
// Replace the URL/path with the actual Freightos API endpoint from their documentation

import fetch from "node-fetch";

export async function getShippingQuote(req, res) {
  try {
    const response = await fetch("https://api.freightos.com/your/real/endpoint", {
      method: "GET", // or POST depending on Freightos endpoint
      headers: {
        "Content-Type": "application/json",
        "Authorization": `Bearer ${process.env.FREIGHTOS_API_KEY}` // Auth header
      }
    });

    if (!response.ok) {
      return res.status(response.status).json({ error: "Freightos API error" });
    }

    const data = await response.json();
    return res.json(data);

  } catch (err) {
    return res.status(500).json({ error: "Server error", details: err.message });
  }
}

 

Frontend Calling Your Backend Route

 

// Example frontend call from a Bolt.new component

async function fetchQuote() {
  const res = await fetch("/api/getShippingQuote");
  const data = await res.json();
  console.log(data); // Display results in UI
}

 

Important Integration Notes

 

• Never call Freightos directly from the browser. You would expose your API key.
• All Freightos requests must run on your Bolt.new server runtime.
• Follow Freightos’ rate limits — they will reject too many calls.
• Validate request bodies carefully; Freightos has strict schemas.

 

End‑to‑End Flow

 

• User clicks “Get Quote.”
• Your frontend calls your Bolt.new backend route.
• Your backend calls Freightos with the stored API key.
• Your backend returns normalized data to the frontend.
• Frontend renders pricing / shipping options.

 

This approach is production‑valid and works both inside Bolt.new and when you later deploy the project outside Bolt to real infrastructure.