No description, website, or topics provided.
Switch branches/tags
Nothing to show
Latest commit e93624b Jul 14, 2015 @dmdigital dmdigital Update
Failed to load latest commit information.
APIs Timers changes May 6, 2015
Old Track setup Jan 27, 2015
.gitignore First draft Jul 12, 2013 Update Jul 14, 2015

Timeneye API 10.0 -

*** This API refers to ***

*** Looking for APIs? Click here ***


Timeneye Time Tracking is a time tracking and reporting web app meant to be extremely simple and usable even for the most recalcitrant user.

Timeneye can be used from the web (, from the Android mobile app and from the iOS mobile app.

Timeneye integrates with Basecamp, allowing users to track time directly from Basecamp commenting on their to-dos with the time spent on them.

API System

You can integrate your apps with Timeneye, offering time tracking capabilities directly from there, using the public Timeneye API


The API is currently in development, with new endpoints being added over time. Currently, the 10.0 version of the API allows third-party apps to manage projects, users and entries.


The API supports an OAuth 2.0 flow. External applications needs to register at to obtain their clientId and clientSecret, and set their redirectUri where users should be redirected upon authentication.

  • External applications redirect the user to a specific page on Timeneye:[clientId]
  • User authorizes the application to access its Timeneye data
  • User is redirected to the application's redirectUri with an additional code parameter
  • The application exchanges the code parameter with an accessToken using the endpoint. This request has to be made specifying a specific header: Authorization: Basic XXX, where XXX is base64('[clientId]:[clientSecret]') and setting the appropriate code and clientId GET query parameters.
  • A JSON structure is returned, containing accessToken, refreshToken and expiration.
  • Subsequent calls can be made using the accessToken set in a specific header: Bearer: [accessToken].

API calls are made throught https.

Data format

The API responses are characterized by a HTTP code (we use a set of about 10 possible response codes) and a JSON payload (when necessary)

Dates are in the MySQL format, GMT: YYYY-MM-DD HH:mm:ss

Available sections

Help us make it better

Please tell us how we can make the API better. If you have a specific feature request or if you found a bug, please use GitHub issues. Fork these docs and send a pull request with improvements.