Nokotime Noko API
★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer42 EndpointsREST
For Agents
Log time entries, manage projects and timers, approve hours in bulk, and pull invoice and expense data from Noko time tracking on behalf of freelancers and agencies.
Use for: I need to log a time entry for 90 minutes against the Acme Co redesign project, List all unapproved time entries from last week so I can review them before invoicing, Mark all approved entries on project 4567 as invoiced after Stripe payment confirms, Start a timer for the discovery call I just joined
Not supported: Does not handle invoice PDF generation, payment collection, or payroll — use for time tracking, project hours, and entry approval only.
Jentic publishes the only available OpenAPI specification for Noko API, keeping it validated and agent-ready. Noko (formerly Freckle) is a time-tracking platform that helps freelancers, agencies, and teams log billable hours against projects, clients, and tasks, then turn those hours into invoices and reports. The API exposes time entries, projects, project groups, tags, timers, users, teams, invoices, and expenses, with bulk approval and invoicing workflows for client billing. Account holders use it to integrate Noko with billing tools, project management apps, and reporting dashboards.
Install Jentic One Beta
Connect the Noko API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Noko 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.
Create, edit, and delete time entries with project, tag, and billable rate metadata
Approve or unapprove time entries individually or in bulk before invoicing
Mark entries as invoiced when they are billed to a client through external accounting
Manage projects, project groups, and tags used to categorise tracked time
Start, pause, and stop running timers attached to specific projects
Pull invoice and expense records to reconcile Noko data with accounting systems
Manage team membership and per-user billable hours visibility
Use Cases
Patterns agents use Noko API for, with concrete tasks.
★ Agency timesheet approval workflow
Agency owners approving consultant hours before invoicing need to see entries grouped by project and approve them in bulk rather than clicking each one. The Noko API exposes /entries with filtering by project and approval status, plus PUT /entries/approved for bulk approval, so an agent can present a weekly digest and apply approvals in a single call. This replaces the manual click-through-each-entry flow that scales poorly past 50 hours per week.
List unapproved entries for project 4567 from last week, then call PUT /entries/approved with the entry IDs to approve them all
Project profitability reporting
Freelancers and agencies tracking margin per project pull tracked hours, billable rates, and expenses from Noko to compare against fixed-fee budgets. The /entries, /projects, and /expenses endpoints together provide hours-by-project, rate-by-user, and reimbursable cost data that an agent can roll up into a profitability dashboard. Noko's tag system lets the agent slice further by activity type such as discovery, design, or development.
Pull all entries for project 4567, sum the hours by tag, multiply by each user's billable rate, and compare against the project budget
Stripe-to-Noko invoice reconciliation
When a Stripe payment lands for a tracked-hours invoice, the corresponding Noko entries should be marked as invoiced so they don't appear in next week's billing draft. The Noko /entries/marked_as_invoiced endpoint accepts a list of entry IDs, allowing an agent to flip the invoiced flag in a single call once the Stripe webhook fires. This closes the loop between accounting and time tracking without manual reconciliation.
When Stripe payment_intent.succeeded fires for invoice INV-203, call PUT /entries/marked_as_invoiced with the linked Noko entry IDs
AI agent time logging on meeting end
An AI agent watching a calendar can automatically log meeting time to the right Noko project when a call ends. Through Jentic, the agent searches 'create a time entry', loads POST /entries, and submits the duration with the matched project and tag. This eliminates the after-meeting context switch that causes most freelancers to lose 10-15% of their billable hours.
Through Jentic, search 'create a time entry', load POST /entries, and submit a 60-minute entry against project 'Acme Discovery' with tag 'meeting'
Key Endpoints
42 endpoints — jentic publishes the only available openapi specification for noko api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/entries
List time entries with filters
POST
/entries
Create a time entry
PUT
/entries/approved
Bulk-approve a set of entries
PUT
/entries/marked_as_invoiced
Mark entries as invoiced after billing
GET
/projects
List projects
POST
/projects
Create a project
GET
/timers
List timers
GET
/users
List users on the account
GET
/entries
List time entries with filters
POST
/entries
Create a time entry
PUT
/entries/approved
Bulk-approve a set of entries
PUT
/entries/marked_as_invoiced
Mark entries as invoiced after billing
GET
/projects
List projects
POST
/projects
Create a project
GET
/timers
List timers
GET
/users
List users on the account
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Noko personal access tokens are stored encrypted in the Jentic vault. Agents receive scoped access — raw bearer tokens never appear in the agent's context or logs.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create a time entry') and Jentic returns the matching Noko operation with its input schema, so the agent calls POST /entries without browsing docs.
Time to first call
Direct Noko integration: 2-3 days for auth, entry pagination, and bulk approval handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Noko API through Jentic.
Why is there no official OpenAPI spec for Noko API?
Noko does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Noko API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Noko API use?
Noko uses HTTP bearer authentication. You generate a personal access token in the Noko web app and pass it in the Authorization header. Through Jentic, the token is stored in the encrypted vault and never enters the agent's prompt context.
Can I approve multiple Noko time entries in a single call?
Yes. PUT /entries/approved accepts an array of entry IDs and approves them in one request, while PUT /entries/unapproved reverses the action. Use /entries/{id}/approved for single-entry approval when reviewing entries one at a time.
What are the rate limits for the Noko API?
Noko's published documentation does not state hard rate limits in the spec. Avoid polling /entries more than once per minute and prefer filtered queries over pulling the full entry list, especially for accounts with thousands of historical entries.
How do I log a time entry through Jentic?
Install the SDK with pip install jentic, then search 'create a time entry', load POST /entries, and execute with the project ID, minutes, and date. The full flow runs without you handling the Noko bearer token in your code.
Can the Noko API generate invoices from tracked hours?
Noko stores invoice records and entry-to-invoice associations but does not generate PDFs or send invoices to clients. Pair the /invoices read endpoints with an accounting API such as QuickBooks or Stripe to generate and deliver the invoice.
GET STARTED