Try it with Bruno
Download a ready-to-run Bruno collection with every Transactional API operation, and make your first calls in minutes.
The fastest way to see how the Transactional API behaves is to call it. We publish a ready-to-run collection for Bruno, a free, open-source API client: every operation on these pages, with the request already built, the token handled for you, and a test that tells you whether the call worked.
Download the Transactional API collection
A zip file with the Bruno collection: one folder per service, split into reads and writes.
What's in the collection
| Folder | What it contains |
|---|---|
01 Authentication (Security V1_2) | GetToken (run this first), GetUser, GetTimeRegistrationSettings |
02 CRM V1_4 … 09 Transaction V1_0 | One folder per service, each split into Reads and Writes (changes data) |
Every request has a Docs tab with what it does and its parameters, and a Tests tab that checks the result.
Get started
Install Bruno
Download Bruno from usebruno.com and install it. No account is needed.
Open the collection
Unzip the download. In Bruno, choose Open Collection and select the unzipped folder.
Fill in the environment
Select the TimeLog environment (top right) and set baseUrl to your TimeLog address,
https://app{server-number}.timelog.com/{account}. Then set the secrets username and password of the TimeLog
user the integration runs as. Bruno keeps secrets on your machine only.
Get a token
Run 01 Authentication / GetToken. It stores the token, and every other request uses it automatically for the next 12 hours. See Authentication.
Make your first call
Open any request under Reads and run it. The Tests tab shows whether ResponseState is Success; the
response shows the data in Return.
How the requests are built
- Simple parameters are pre-filled with neutral values (
false,0, page1, page size10, an empty GUID). Replace IDs with real ones from your account before running. - Object parameters in write requests have every field commented out. Uncomment the fields you need and keep the order shown. Run as-is, a write is a safe dry run: it answers with the validation messages for the required fields.
- CRM requests are chained: a customer search stores the customer's GUID and ID, so you can go straight on to GetCustomerByGUID and GetContactsByCustomerPaged.
- InsertCustomer with external key (CRM writes) shows how to link a TimeLog record to its ID in another system.
Reading the result
A failed call still returns HTTP 200: the Tests tab checks ResponseState for you. When it fails, look at
ErrorCode and Messages in the response, and find the code in Responses and errors.