Keep your Harvest API integrations — change one URL

Updated 2026-10-21 · Written by the Feestead team

Many teams built scripts, dashboards and invoicing jobs on the Harvest v2 API. Feestead speaks the same API for time tracking data, so moving off Harvest doesn't mean rewriting them.

What changes

- https://api.harvestapp.com/v2/time_entries
+ https://feestead.com/v2/time_entries

Authorization: Bearer <Feestead token from Settings>
Harvest-Account-Id: <your Feestead account ID>

The Harvest-Account-Id header, access_token/account_id query parameters, pagination envelope (per_page, total_pages, next_page, links.next) and object shapes match Harvest's. The API is also available under /api/v2/.

Supported endpoints

Creating time entries works with hours (duration), started_time/ended_time, or neither (starts a timer) — like Harvest.

Not supported (yet)

Invoices, estimates, expenses, roles and user assignments endpoints. If your integration needs one of these, tell us — real use cases decide what we build next.

Example: weekly hours by project in Python

import requests
BASE = "https://feestead.com/v2"   # was https://api.harvestapp.com/v2
H = {"Authorization": "Bearer hw_...", "Harvest-Account-Id": "1"}

url, totals = f"{BASE}/time_entries?from=2026-10-12&to=2026-10-18", {}
while url:
    page = requests.get(url, headers=H).json()
    for e in page["time_entries"]:
        totals[e["project"]["name"]] = totals.get(e["project"]["name"], 0) + e["hours"]
    url = page["links"]["next"]
print(totals)

Migrating an integration safely

1. Import your Harvest account so IDs and data exist in Feestead.
2. Create a token in Settings → API access.
3. Run your script against Feestead in read-only mode and compare output with Harvest.
4. Switch writes once totals match.

Note: record IDs differ between Harvest and Feestead. If your script stores Harvest IDs, map them by name or re-fetch after import.