Bolt.new AI and Receipt Bank (now Dext) integration: Step-by-Step Guide 2025

To integrate Bolt.new with Dext (formerly Receipt Bank), you don’t “connect Bolt to Dext.” Instead, you build a normal full‑stack app inside Bolt that calls the Dext Prepare API using standard HTTPS requests. Dext does not offer a public self‑serve API anymore, so the only valid path is: you must request API access from Dext, get API credentials (client ID/secret or token), and then use those credentials in Bolt.new via environment variables. Once credentials exist, integration is just REST calls (upload receipts, fetch extracted data, etc.). Bolt.new simply executes your code — it doesn’t provide special connectors.

 

How to integrate Bolt.new with Dext (Receipt Bank)

 

If you want your Bolt.new project to interact with Dext, you treat Dext like any external SaaS: authenticate with their API, send files via their ingestion endpoint, poll or subscribe for extraction results, and store those in your own backend. Because Dext offers API access only through their partner program, the first and required step is to obtain API credentials from Dext support. After that, the process is straightforward: store your API keys in Bolt.new env variables, then use normal fetch/axios calls in Node to hit Dext endpoints.

• Dext has no open/public API docs on the web anymore. Their Prepare API is accessible only with partner approval.
• Bolt.new cannot bypass that. Your code inside Bolt still needs real credentials.
• Once Dext gives you the API specs + auth method, you implement it as a normal REST integration.

 

Step-by-step (realistic, working approach)

 

This is the safest and correct method to integrate Bolt.new with Dext using an API‑driven workflow.

• Request API access from Dext: Ask Dext support for “Dext Prepare API partner access.” They will provide API endpoints and an authentication method (usually OAuth2 client credentials or an API token).
• Create a Bolt.new project and open the Environment Variables panel. Add:
  • DEXT_CLIENT_ID or DEXT_API_KEY
  • DEXT_CLIENT_SECRET (if applicable)
• Implement authentication: Dext usually uses one of these:
  • OAuth2 client\_credentials to obtain an access token
  • A static API token passed in an Authorization header
• Implement receipt upload: In almost all Dext integrations, you upload receipts as files via multipart/form-data to a “documents” or “ingestion” endpoint.
• Poll the extraction result or receive callbacks if Dext enables webhooks for your account.

 

Example: Node.js integration scaffold inside Bolt.new

 

This example shows the pattern. The exact URL and fields come from Dext after they grant access. This is how you structure the code inside Bolt.new.

// server/dextClient.js
// Pattern for integrating with Dext from a Bolt.new Node backend

import axios from "axios";
import FormData from "form-data";
import fs from "fs";

// Example: OAuth2 client credentials flow (Dext may vary)
async function getAccessToken() {
  const resp = await axios.post("https://api.dext.com/oauth/token", {
    grant_type: "client_credentials",
    client_id: process.env.DEXT_CLIENT_ID,
    client_secret: process.env.DEXT_CLIENT_SECRET
  });

  return resp.data.access_token;
}

export async function uploadReceipt(filePath) {
  const token = await getAccessToken();

  const form = new FormData();
  form.append("file", fs.createReadStream(filePath));

  const resp = await axios.post("https://api.dext.com/prepare/documents", form, {
    headers: {
      Authorization: `Bearer ${token}`,
      ...form.getHeaders()
    }
  });

  return resp.data; // Dext returns a document ID
}

export async function fetchReceiptStatus(documentId) {
  const token = await getAccessToken();

  const resp = await axios.get(
    `https://api.dext.com/prepare/documents/${documentId}`,
    {
      headers: {
        Authorization: `Bearer ${token}`
      }
    }
  );

  return resp.data; // Contains extraction status + parsed fields
}

 

How you use this inside Bolt.new

 

In a typical project, you add an API route like /api/upload that receives a file from the frontend and then calls uploadReceipt(). Later another route calls fetchReceiptStatus() to check extraction results. Bolt.new simply runs this Node code inside its environment — nothing special required.

• The frontend uploads the image/PDF.
• Your Bolt backend sends it to Dext.
• Dext processes it and returns structured data.

 

Important constraints and realities

 

• Dext does not provide self‑serve API credentials. You must request them.
• Bolt.new cannot talk to Dext without valid credentials.
• No special Bolt integration exists. Everything is standard REST.
• Production deployment outside Bolt should preserve the same patterns: env variables, HTTPS, OAuth2/token auth, webhook endpoints if available.

 

This is the correct and realistic way to integrate Dext with a Bolt.new project today.