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

To integrate Bolt.new with Everhour, you don’t “connect” Bolt itself. Instead, you build a small full‑stack app inside bolt.new (Node, Next.js, etc.) that talks to Everhour’s real public REST API using an Everhour API key stored in environment variables. Bolt is just your development workspace; the integration is done through normal HTTP requests. The key steps are: get an Everhour API key, store it as an env var in Bolt, call Everhour’s REST endpoints (for time entries, projects, timers, etc.), and then build UI/actions that trigger those API calls.

 

What Everhour Actually Provides

 

Everhour exposes a real REST API. There is no OAuth, no SDK, no webhook system — just API-key based authorization. You pass the key via HTTP header X-Api-Key. That’s the only officially documented method.

• Authentication: static API key
• Protocol: REST (JSON)
• Common endpoints: time entries, tasks, users, current timer

 

Step‑by‑Step: Wiring Everhour inside Bolt.new

 

Below is the correct, production-valid flow.

• Create a Bolt.new workspace using the Node.js or Next.js template.
• Add an environment variable in Bolt’s env panel:
  X_EVERHOUR_API\_KEY = your-api-key-here
• Create a backend route inside your Bolt project to call Everhour. The backend is needed so your API key never appears in the browser.
• Call Everhour’s REST API using fetch with the correct header.
• Expose safe routes to your frontend or AI actions (Bolt’s agent can call your own backend route, not Everhour directly).

 

Example backend API route (Next.js /api/time-entries)

 

// app/api/time-entries/route.js
export async function GET() {
  const apiKey = process.env.X_EVERHOUR_API_KEY  // Your Everhour API key

  const res = await fetch("https://api.everhour.com/v1/time-entries", {
    method: "GET",
    headers: {
      "Content-Type": "application/json",
      "X-Api-Key": apiKey
    }
  })

  if (!res.ok) {
    return new Response(JSON.stringify({ error: "Failed to fetch Everhour data" }), { status: 500 })
  }

  const data = await res.json()
  return new Response(JSON.stringify(data), { status: 200 })
}

 

Why this works

 

Everhour only requires the API key header. Bolt.new runs your backend routes on its server sandbox, so you safely store the API key in environment variables. Your frontend or Bolt AI agent sends requests to /api/time-entries, and the backend securely forwards the call to Everhour.

• No credentials leak — API key never reaches the browser.
• Simple testing — you can hit your route directly in Bolt’s preview.
• Easy to extend — call other Everhour endpoints the same way.

 

Example UI call from the frontend

 

// In a Next.js client component
async function loadEntries() {
  const res = await fetch("/api/time-entries")  // hitting your backend, not Everhour directly
  const data = await res.json()
  console.log(data)
}

 

Common Everhour Endpoints You Can Use

 

• GET https://api.everhour.com/v1/time-entries
• POST https://api.everhour.com/v1/time-entries
• GET https://api.everhour.com/v1/users/me
• GET https://api.everhour.com/v1/timers/current
• POST https://api.everhour.com/v1/timers/start

You can wire all of these the same way — backend route in Bolt, pass API key in header, return JSON to your UI or your AI agent.

 

How Bolt.new AI fits into this

 

Bolt’s AI can help scaffold the routes, build UI, and test calls, but it does not connect to Everhour directly. You integrate by writing real code that calls Everhour’s REST API from your Bolt backend, and the AI can generate or modify that code for you.

That’s the complete and correct way to integrate Everhour with a Bolt.new project.