How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hakuna Time Entries API

Recorded blocks of worked time

Hakuna Time Entries API is one of 10 APIs that Hakuna publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Time Entries. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://app.hakuna.ch/api/v1.

5 operations 2 paths 7 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://app.hakuna.ch/api/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Hakuna Time Entries API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (AuthToken). By default, every request must be authenticated.

  • AuthToken — Personal API token managed under "My Settings". Organization endpoints require a separate organization-level token; management endpoints require an admin token.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Time Entries 5

Recorded blocks of worked time

GET
/time_entries
List time entries
listTimeEntries → 200401429
POST
/time_entries
Create a time entry
createTimeEntry body → 201401422429
GET
/time_entries/{id}
Get a time entry
getTimeEntry 1 param → 200401404429
PATCH
/time_entries/{id}
Update a time entry
updateTimeEntry 1 param body → 200401404422429
DELETE
/time_entries/{id}
Delete a time entry
deleteTimeEntry 1 param → 204401404429

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are TimeEntry (9 properties), TimeEntryInput (6 properties), Project (4 properties), User (4 properties). Each schema is shown below with its type and property counts.

TimeEntry
object
A recorded block of worked time.
9 properties
TimeEntryInput
object
6 properties
User
object
A user of the account.
4 properties
Error
object
JSON error object with a descriptive message.
1 property
Client
object
A client that projects belong to.
3 properties
Project
object
A project that time can be tracked against.
4 properties
Task
object
A categorization task.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hakuna-time-entries-api-openapi.yml Raw ↑

Other APIs Hakuna publishes across the network.

Hakuna Absences API
Hakuna Company API
Hakuna Management API
Hakuna Organization API
Hakuna Overview API
Hakuna Projects API
Hakuna Tasks API
Hakuna Timer API
Hakuna Users API
Where this information came from

This is an independent, third-party profile of Hakuna Time Entries API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.