List contact persons

Returns every contact person of the account in one response.

Returns all contacts of all customers — active and inactive alike, with no way to tell them apart — ordered by ID, in ONE response: no paging is applied and the TAF paging properties read TotalRecord "0" / TotalPage "0". There are no filters (by customer, name or e-mail). ShownName on this operation is the full name of the contact's OWNER, not of the contact; Address3 is always null.

Use it to:

Build a ContactID map (by name / e-mail + CustomerID) before setting project or invoice contacts

Not for:

Contacts of one customer only — no filter exists; filter CustomerID client-side.

Behaviour:

Idempotent.
Safe to retry.
Changes are visible to the next read immediately.

Next: POST /v1/customer/create, PUT /v1/project/{projectID}

See also: POST /v1/contact/create

Not yet documented: response → pagination.

curl -X GET "https://app3.timelog.com/your-account/api/v1/contact" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

import requests
import json

url = "https://app3.timelog.com/your-account/api/v1/contact"
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/contact", {
  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/contact", 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/contact')
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": {
        "ID": 123,
        "GUID": "123e4567-e89b-12d3-a456-426614174000",
        "FirstName": "null",
        "LastName": "null",
        "Phone": "null",
        "Fax": "null",
        "Email": "null",
        "Department": "null",
        "Address": "null",
        "Address2": "null",
        "Address3": "null",
        "ZipCode": "null",
        "City": "null",
        "State": "null",
        "CountryID": 123,
        "CustomerID": 123,
        "Initials": "example_string",
        "PrivatePhone": "null",
        "Mobile": "null",
        "JobTitle": "null",
        "ProfessionalTitle1": "example_string",
        "ProfessionalTitle2": "example_string",
        "Salutation": "example_string",
        "ShownName": "null"
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}

GET

/v1/contact

GET

Base URLstring

Target server for requests. Edit to use your own host.

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.

Request Preview

Response

Response will appear here after sending the request

Authentication

header

Authorizationstring

Required

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

Entitiesarray

Omitted (not []) when the list is empty.

Linksarray

Was this page helpful?