Get my home and work addresses
Returns the caller's own home address and the company's address, as one-tap start / end addresses for a trip.
Two suggestions: the CALLER's home address from their user profile (Type 2 Home — always returned, with empty fields when no home address is stored) and the account's own company address (Type 0 Internal — the CRM customer configured as the company itself; absent when that customer has no country). Use FullDetailAddress as the mileage StartAddress / EndAddress. Personal data: the response contains the caller's home address and is scoped to the caller.
Use it to:
- Mobile mileage form: prefill 'from home' / 'to office' for a commute-style trip
Not for:
- Another employee's address — not available through this API
- Customer or project addresses —
GET /v1/address/search
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
Next: POST /v1/mileage-registration
See also: GET /v1/address/search
curl -X GET "https://app3.timelog.com/your-account/api/v1/address/home-work" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v1/address/home-work"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v1/address/home-work", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://app3.timelog.com/your-account/api/v1/address/home-work", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v1/address/home-work')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"Entities": [
{
"Properties": {
"TypeName": "Home",
"Name": null,
"Address": "",
"Address2": "",
"Address3": null,
"Postcode": "",
"City": "",
"State": null,
"CountryName": null,
"Type": 2,
"FullAddress": "",
"FullDetailAddress": ""
}
},
{
"Properties": {
"TypeName": "Internal",
"Name": "Name_Customer140",
"Address": "Adresse",
"Address2": "Adresse2",
"Address3": "Adresse3",
"Postcode": "PostCode",
"City": "City",
"State": "State",
"CountryName": "Storbritannien",
"Type": 0,
"FullAddress": "Adresse, Adresse2, Adresse3, PostCode, City, State, Storbritannien",
"FullDetailAddress": "Name_Customer140, Adresse, Adresse2, Adresse3, PostCode, City, State, Storbritannien"
}
}
],
"Links": [
{
"Href": "https://app{server-number}.timelog.com/{account}/api/v1/address/home-work",
"Rel": "self"
}
]
}
{
"Message": "Authorization has been denied for this request."
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v1/address/home-work
Target server for requests. Edit to use your own host.
OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.
Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
Not yet documented: how to obtain a token.
Not yet documented: token lifetime.
Responses
Omitted (not []) when the list is empty.