Usage and change policy

These rules apply to all three TimeLog APIs: REST, Transactional and Reporting.

Restrictions

The APIs are available to TimeLog customers on every pricing plan except Starter, to supplement the TimeLog web app. Customers on the Starter plan do not get API access. See What you need for what else has to be in place.

TimeLog monitors how the APIs are used, so that every customer gets a fair share of performance. No strict usage limits are enforced per TimeLog account today.

• Use the APIs responsibly. Partners and customers who call the APIs must keep a reasonable call frequency and avoid large bursts of requests. Narrow each call with its filters instead of reading everything again; for bulk reads, see Sync to a data warehouse.
• TimeLog contacts you before limiting. Before taking action that limits an account's API use, TimeLog reaches out to the employee marked as TimeLog Responsible in that account.
• Talk to us about best practice and performance. Contact TimeLog through timelog.com/en/contact.

Change policy

• Additions can happen without notice. TimeLog may add new methods and properties to any of the APIs at any time, and in some cases announces them in the changelog. Build your integration so that it ignores fields it does not know.
• Breaking changes are announced. Changing or removing existing fields or methods, including changes to a method's signature, is announced in advance in the changelog.