Tools and SDKs
Which clients you can use to try each TimeLog API without writing code, and the .NET SDKs on GitHub.
You do not need to write code to see how an API behaves. Each API has a Try it page with every way to call it, in the order we recommend.
| REST API | Transactional API | Reporting API | |
|---|---|---|---|
| Start here | REST: Try it | Transactional: Try it | Reporting: Try it |
| Ready-made collection | — | Bruno (recommended) | Bruno (recommended) |
| Postman | ✓ | ✓ | ✓ |
| SoapUI | — | ✓ | ✓ |
| In the docs, nothing to install | Playground on every operation page | — | — |
.NET SDKs
TimeLog publishes .NET SDKs for the Transactional and Reporting APIs on GitHub, in TimeLog/TimeLogApiSdk. The APIs do not need .NET: the SDKs are a convenience, and their source shows constructs you can copy to other languages.
| Project | What it is |
|---|---|
TimeLog.TransactionalAPI.SDK | Transactional API client, including token handling across services. |
TimeLog.ReportingAPI.SDK | Reporting API client, with typed default values for parameters. |
TimeLog.ReportingApi.Exporter | A console application that exports Reporting API data to XML or CSV without code. |
TimeLog.API.ConsoleApp | Simple examples that use both SDKs. |
Ready-built libraries are in the repository's Deploy folder.
To be notified when the APIs or their documentation change, choose Watch on the GitHub repository, or follow the changelog.
Was this page helpful?