Letsfreckle Noko (Freckle) Time Tracking API
✓ Official Vendor SpecProductivityTask Managementbearer12 EndpointsREST
For Agents
Log billable time entries, manage projects, and read users, tags, and timers — all through a small, focused REST API.
Use for: Log a one-hour entry against the website redesign project, List my time entries from last week, Update the description on a previously logged entry, Create a new project for a client engagement
Not supported: Does not handle invoicing, payroll, or expense management — use for logging time entries and managing projects, users, tags, and timers only.
Noko (formerly Freckle) is a team time-tracking platform built around projects, tagged time entries, users, and timers. The v2 API lets agents log entries against a project, list and update existing entries, manage projects (including archive/unarchive), and read the user, tag, and timer collections that surround them. The flat resource model and tagging convention make it well-suited to agencies, consultancies, and product teams that want to enforce a tag taxonomy across logged work.
Install Jentic One Beta
Connect the Noko (Freckle) Time Tracking API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Noko (Freckle) Time Tracking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.letsfreckle.com%2Fletsfreckle" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.letsfreckle.com%2Fletsfreckle" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Noko (Freckle) Time Tracking API.
Log a new time entry against a project with date, duration, description, and tags
List and filter time entries by user, project, date range, or tag
Update or delete an existing time entry to correct a logged duration or description
Create new projects and update their billing rate, group, or status
Archive a project to remove it from active selection without deleting historical entries
Unarchive a project when work resumes
Read users, tags, and timers to power dropdowns and reporting
Use Cases
Patterns agents use Noko (Freckle) Time Tracking API for, with concrete tasks.
★ Automated Time Logging from Calendar Events
Convert calendar events into Noko time entries automatically. A scheduled job iterates events with a billable code in the title, calls POST /entries with the matching project_id, duration in seconds, date, and a standard tag set, and skips events already logged. This eliminates the daily ritual of manual time entry for teams whose work maps cleanly to meetings.
For each calendar event today tagged 'billable', call POST /entries with project_id, minutes, date, and tags=['client-meeting'], then return the created entry IDs.
Project Archival on Completion
Archive projects automatically when their parent record in a CRM or PM tool moves to Closed. PUT /projects/{id}/archive moves a project out of the active list while preserving every historical entry for billing and reporting. PUT /projects/{id}/unarchive reverses the move when work resumes — useful when retainer engagements come back online.
When a CRM deal moves to 'Closed Won', call POST /projects with the deal name; when it moves to 'Closed Lost', call PUT /projects/{id}/archive on any matching project.
Weekly Billable Hours Reporting
Pull billable hours per project across a week for invoicing or PTO accruals. GET /entries supports filters by project, user, and date so a single call can return a week's logged time, ready to aggregate by project or tag. The output feeds invoice generation tools, freeing finance from manual exports.
Call GET /entries with from=2026-06-02, to=2026-06-08 and return total minutes per project_id for invoice generation.
AI Agent Time Tracking Assistant
An AI assistant that drafts work logs from chat or email summaries can post entries to Noko via Jentic. Jentic exposes /entries, /projects, and /projects/{id}/archive as discoverable tools so the agent picks the right operation by intent. The Noko bearer token stays in the Jentic vault.
Search for 'log a time entry', load the POST /entries schema, and create the entry with the project_id, minutes, and description supplied by the agent input.
Key Endpoints
12 endpoints — noko (formerly freckle) is a team time-tracking platform built around projects, tagged time entries, users, and timers.
METHOD
PATH
DESCRIPTION
GET
/entries
List time entries
POST
/entries
Create a time entry
PUT
/entries/{id}
Update an existing time entry
DELETE
/entries/{id}
Delete a time entry
GET
/projects
List projects
POST
/projects
Create a new project
PUT
/projects/{id}/archive
Archive a project
PUT
/projects/{id}/unarchive
Unarchive a project
GET
/entries
List time entries
POST
/entries
Create a time entry
PUT
/entries/{id}
Update an existing time entry
DELETE
/entries/{id}
Delete a time entry
GET
/projects
List projects
POST
/projects
Create a new project
PUT
/projects/{id}/archive
Archive a project
PUT
/projects/{id}/unarchive
Unarchive a project
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Noko (Freckle) Time Tracking API by hand means setting up its bearer token auth and coding your own calls to the entries, projects, and timer endpoints. Through Jentic you install once, import the Noko (Freckle) Time Tracking API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Noko puts the entry and project id in the URL path (/entries/{id}, /projects/{id}/archive), so a rule can pin your agent to acting on one entry or project. You choose the operations it may call, so deleting an entry or archiving a project are not included unless you add them.
Credential isolation
Your Noko token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'log a time entry' or 'list entries for a project', and Jentic returns the matching Noko operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Noko (Freckle) Time Tracking API through Jentic.
What authentication does the Noko (Freckle) API use?
Noko uses HTTP Bearer authentication — a personal access token passed as Authorization: Bearer <token>. Tokens are issued from the Noko account integrations page. Through Jentic, the token is held encrypted in the Jentic vault and injected at execution time.
Can I create time entries against an archived project?
No. POST /entries requires a project that is currently active. If you need to log time against historical work, call PUT /projects/{id}/unarchive first, post the entries, then re-archive with PUT /projects/{id}/archive. Existing entries on archived projects remain readable via GET /entries.
What are the rate limits for the Noko API?
Noko applies modest rate limits and returns 429 with a Retry-After header when a client exceeds them. Treat the API as suitable for steady automation rather than burst imports — for example, daily syncs of yesterday's entries rather than re-pulling years of data on every run.
How do I log a time entry through Jentic?
Run pip install jentic, then search for 'log a time entry'. Jentic returns the POST /entries operation. Load its schema, pass project_id, minutes, date (YYYY-MM-DD), description, and tags, then execute. The response includes the created entry id.
Is the Noko API free to use?
API access is included with any paid Noko plan; there is a free trial but no permanent free tier. The API itself does not have a separate per-call price — usage counts against the same plan limits as the web application.
How do tags work on Noko entries?
Tags are free-form strings attached to a POST /entries call; they are created on first use and can be browsed via the tags resource. Most teams agree a tag taxonomy upfront — for example, 'client-meeting', 'support', 'design-review' — so reports group consistently.
GET STARTED