How to Integrate Lovable with Everhour

Everhour API keys are workspace-level credentials — they give access to all data in your Everhour team account, including time entries from all team members. To generate one, log into Everhour and click the team settings icon (gear icon) in the top navigation. Select 'Team Settings' and navigate to the 'API' or 'Integrations' section. Click 'Generate API Key', copy it immediately, and give it a descriptive label like 'Lovable Integration'. Note that API access in Everhour requires a Team plan or above — the free plan does not include API access. If you're on a free account and attempting to use the API, you'll receive 403 Forbidden errors on all requests. Confirm your plan before proceeding. With the key copied, open your Lovable project, click the '+' button, and select the Cloud tab. Navigate to Secrets and click 'Add secret'. Enter EVERHOUR_API_KEY as the name and paste your key as the value. Save it. Unlike other APIs that use Bearer auth, Everhour sends its API key as an X-Api-Key header — your Edge Function will set this custom header on every request.

Everhour's REST API v1 uses the X-Api-Key custom header for authentication. Time entries in Everhour are identified by a composite key — they reference both a project ID and optionally a task ID using Everhour's internal task format (e.g., 'tm:12345' for Trello tasks, 'jira:PROJECT-123' for Jira issues, or plain numeric IDs for Everhour-native tasks). Understanding this task ID format is important if you're integrating with Everhour's PM tool connections. The Edge Function below covers the most valuable operations: listing projects with budget data, fetching team time reports by date range, starting and stopping the timer for the authenticated user, creating manual time entries, and fetching per-project time summaries. The timer endpoints are user-scoped — the start/stop actions apply to the user whose API key is being used.

1// supabase/functions/everhour-proxy/index.ts
2import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
3
4const BASE = "https://api.everhour.com";
5const corsHeaders = {
6  "Access-Control-Allow-Origin": "*",
7  "Access-Control-Allow-Headers": "authorization, x-client-info, apikey, content-type",
8};
9
10serve(async (req) => {
11  if (req.method === "OPTIONS") {
12    return new Response("ok", { headers: corsHeaders });
13  }
14  const apiKey = Deno.env.get("EVERHOUR_API_KEY");
15  if (!apiKey) {
16    return new Response(JSON.stringify({ error: "EVERHOUR_API_KEY not set" }), {
17      status: 500, headers: { ...corsHeaders, "Content-Type": "application/json" },
18    });
19  }
20  const authHeaders = { "X-Api-Key": apiKey, "Content-Type": "application/json" };
21  const { action, params = {} } = await req.json();
22  let resp;
23
24  switch (action) {
25    case "list_projects": {
26      const q = new URLSearchParams({ limit: String(params.limit || 100) });
27      resp = await fetch(`${BASE}/projects?${q}`, { headers: authHeaders });
28      break;
29    }
30    case "get_project":
31      resp = await fetch(`${BASE}/projects/${params.projectId}`, { headers: authHeaders });
32      break;
33    case "list_time": {
34      const q = new URLSearchParams();
35      if (params.from) q.set("from", params.from);
36      if (params.to) q.set("to", params.to);
37      if (params.userId) q.set("user", params.userId);
38      resp = await fetch(`${BASE}/team/time?${q}`, { headers: authHeaders });
39      break;
40    }
41    case "get_project_time": {
42      const q = new URLSearchParams();
43      if (params.from) q.set("from", params.from);
44      if (params.to) q.set("to", params.to);
45      resp = await fetch(`${BASE}/projects/${params.projectId}/time?${q}`, { headers: authHeaders });
46      break;
47    }
48    case "start_timer":
49      resp = await fetch(`${BASE}/timers/current`, {
50        method: "POST", headers: authHeaders,
51        body: JSON.stringify({ task: { id: params.projectId }, ...(params.taskId && { task: { id: params.taskId } }) }),
52      });
53      break;
54    case "stop_timer":
55      resp = await fetch(`${BASE}/timers/current`, { method: "DELETE", headers: authHeaders });
56      break;
57    case "get_timer":
58      resp = await fetch(`${BASE}/timers/current`, { headers: authHeaders });
59      break;
60    case "add_time":
61      resp = await fetch(`${BASE}/time`, {
62        method: "POST", headers: authHeaders,
63        body: JSON.stringify({
64          date: params.date, time: params.timeSeconds,
65          task: { id: params.projectId },
66          ...(params.comment && { comment: params.comment }),
67        }),
68      });
69      break;
70    case "list_members":
71      resp = await fetch(`${BASE}/team/members`, { headers: authHeaders });
72      break;
73    default:
74      return new Response(JSON.stringify({ error: `Unknown action: ${action}` }), {
75        status: 400, headers: { ...corsHeaders, "Content-Type": "application/json" },
76      });
77  }
78
79  const data = await resp.json();
80  return new Response(JSON.stringify(data), {
81    status: resp.status, headers: { ...corsHeaders, "Content-Type": "application/json" },
82  });
83});

Everhour's budget data is exposed on each project object — the budget field contains the type ('time' for hours-based, 'money' for currency-based) and the value (in seconds for time budgets). By comparing the budget value to total time logged, you can calculate burn percentage and project health. For trend analysis, fetching time entries by week over the past month shows logging velocity. The dashboard component generates a project health overview that's useful for weekly agency reviews: color-coded burn indicators, time remaining calculations, and a pace indicator showing whether the current logging rate will exceed budget before the project end date.

The most engaging part of a time tracking integration is real-time timer control — users should be able to start a timer, see it counting up, and stop it to log the session. The Everhour timer API provides start (POST /timers/current), stop (DELETE /timers/current), and status (GET /timers/current) endpoints. The GET endpoint returns the current running timer state including the start time, which your frontend can use to calculate elapsed time client-side without additional API calls. For manual time entry (logging time after the fact), the Edge Function's add_time action creates a backdated entry on any past date. Combine this with a date picker and time input to create a manual log panel that team members can use to enter hours for work done without the timer running — a common scenario for meetings, calls, and focus sessions that happened before the user remembered to start the timer.