GetEmployeesRaw

Reporting API: Returns the account's employees with personal and work contact data, employment dates, department, cost price and default rate.


API	Reporting API (raw extracts)
Endpoint	`POST https://app{server-number}.timelog.com/{account}/Service.asmx`
SOAPAction	`http://www.timelog.com/ws/tlp/v4_4/GetEmployeesRaw`
Content-Type	`text/xml; charset=utf-8`
Authentication	`siteCode`, `apiID` and `apiPassword` as the first three parameters. See Authentication
Changes data	No. Safe to retry.
Paging	No: the whole result comes in one response. Narrow it with the filters.

How it works

Filters combine with AND: employee id, initials, department and status. HIGHEST-sensitivity extract of the API: names, work e-mail and phones, PRIVATE phone and home address, employment / resignation dates, employee number, LOGIN user name, current cost price and default billing rate for every employee. CostPrice is a culture-formatted STRING with an odd fallback.

Parameters

Each parameter has one label: Required, Conditional (required depending on other values) or Optional. Send them in the order shown.

siteCodestring

Required

Your account's site code, from the Reporting API settings.

apiIDstring

Required

The Reporting API ID, from the Reporting API settings.

apiPasswordstring

Required

The Reporting API password, from the Reporting API settings.

employeeIDinteger

Required

Employee id. 0 = no filter.

initialsstring

Required

Empty string = no filter.

departmentIDinteger

Required

The employee's current department, exact - sub-departments are NOT included. 0 = no filter.

statusinteger

Required

1 active, 0 inactive, any negative value = all. Values > 1 match nothing. Default -1 recommended.

Request

POST /{account}/Service.asmx HTTP/1.1
Host: app{server-number}.timelog.com
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.timelog.com/ws/tlp/v4_4/GetEmployeesRaw"

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:tlp="http://www.timelog.com/ws/tlp/v4_4">
  <soap:Body>
    <tlp:GetEmployeesRaw>
      <tlp:siteCode>{siteCode}</tlp:siteCode>
      <tlp:apiID>{apiID}</tlp:apiID>
      <tlp:apiPassword>{apiPassword}</tlp:apiPassword>
      <tlp:employeeID>0</tlp:employeeID>
      <tlp:initials></tlp:initials>
      <tlp:departmentID>0</tlp:departmentID>
      <tlp:status>-1</tlp:status>
    </tlp:GetEmployeesRaw>
  </soap:Body>
</soap:Envelope>

curl -X POST "https://app{server-number}.timelog.com/{account}/Service.asmx" \
  -H "Content-Type: text/xml; charset=utf-8" \
  -H 'SOAPAction: "http://www.timelog.com/ws/tlp/v4_4/GetEmployeesRaw"' \
  --data-binary @request.xml

import requests

URL = "https://app{server-number}.timelog.com/{account}/Service.asmx"
SOAP_ACTION = '"http://www.timelog.com/ws/tlp/v4_4/GetEmployeesRaw"'

envelope = """<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:tlp="http://www.timelog.com/ws/tlp/v4_4">
  <soap:Body>
    <tlp:GetEmployeesRaw>
      <tlp:siteCode>{siteCode}</tlp:siteCode>
      <tlp:apiID>{apiID}</tlp:apiID>
      <tlp:apiPassword>{apiPassword}</tlp:apiPassword>
      <tlp:employeeID>0</tlp:employeeID>
      <tlp:initials></tlp:initials>
      <tlp:departmentID>0</tlp:departmentID>
      <tlp:status>-1</tlp:status>
    </tlp:GetEmployeesRaw>
  </soap:Body>
</soap:Envelope>"""

response = requests.post(
    URL,
    data=envelope.encode("utf-8"),
    headers={"Content-Type": "text/xml; charset=utf-8", "SOAPAction": SOAP_ACTION},
    timeout=300,
)
rows = parse_result(response)  # see "Responses and errors"

Replace every {…} placeholder with your own value.

Response

The result is an XML document inside GetEmployeesRawResult: a tlp:Employees root with one tlp:Employee element per record. Check the response format first: the same slot also carries the empty result and errors.

Order: First name, then last name; no unique tie-breaker.

tlp:EmployeeEmployeeRaw[]

One element per record. Fields without a value are left out of the element, so treat every field as optional.

Example response

HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <GetEmployeesRawResponse xmlns="http://www.timelog.com/ws/tlp/v4_4">
      <GetEmployeesRawResult>
        <tlp:Employees xmlns:tlp="http://www.timelog.com/XML/Schema/tlp/v4_4">
          <tlp:Employee ID="1001">
            <tlp:EmployeeUserID>12</tlp:EmployeeUserID>
            <tlp:FirstName>Anna</tlp:FirstName>
            <tlp:LastName>Example</tlp:LastName>
            <tlp:FullName>Anna Example</tlp:FullName>
            <tlp:Initials>ABC</tlp:Initials>
            <tlp:Title>Example text</tlp:Title>
            <tlp:Email>anna.example@example.com</tlp:Email>
            <tlp:Phone>+45 00 00 00 00</tlp:Phone>
            <tlp:Mobile>+45 00 00 00 00</tlp:Mobile>
            <tlp:PrivatePhone>+45 00 00 00 00</tlp:PrivatePhone>
            <tlp:Address>Example text</tlp:Address>
            <tlp:ZipCode>1000</tlp:ZipCode>
            <tlp:City>Copenhagen</tlp:City>
            <tlp:Status>1</tlp:Status>
            <tlp:HiredDate>2026-10-01T00:00:00</tlp:HiredDate>
            <tlp:TerminatedDate>2026-12-31T00:00:00</tlp:TerminatedDate>
            <tlp:DepartmentNameID>12</tlp:DepartmentNameID>
            <tlp:DepartmentName>Example department</tlp:DepartmentName>
            <tlp:WorkWeek>Example text</tlp:WorkWeek>
            <tlp:EmployeeTypeID>12</tlp:EmployeeTypeID>
            <tlp:EmployeeTypeName>Example employee type</tlp:EmployeeTypeName>
            <tlp:EmployeeNo>1001</tlp:EmployeeNo>
            <tlp:Username>anna.example</tlp:Username>
            <tlp:CostPrice>Example text</tlp:CostPrice>
            <tlp:LegalEntityID>12</tlp:LegalEntityID>
            <tlp:ApprovalManagerUserID>12</tlp:ApprovalManagerUserID>
            <tlp:ApprovalManagerEmployeeID>12</tlp:ApprovalManagerEmployeeID>
            <tlp:DefaultHourlyRateID>12</tlp:DefaultHourlyRateID>
            <tlp:DefaultHourlyRate>950.0000</tlp:DefaultHourlyRate>
            <tlp:DefaultHourlyRateCurrency>DKK</tlp:DefaultHourlyRateCurrency>
          </tlp:Employee>
        </tlp:Employees>
      </GetEmployeesRawResult>
    </GetEmployeesRawResponse>
  </soap:Body>
</soap:Envelope>

HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <GetEmployeesRawResponse xmlns="http://www.timelog.com/ws/tlp/v4_4">
      <GetEmployeesRawResult>
        <tlp:Employees resultEmpty="true" xmlns:tlp="http://www.timelog.com/XML/Schema/tlp/v4_4"></tlp:Employees>
      </GetEmployeesRawResult>
    </GetEmployeesRawResponse>
  </soap:Body>
</soap:Envelope>

Example error

Wrong credentials, or a call over plain HTTP:

HTTP/1.1 401 Unauthorized
Content-Type: text/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <GetEmployeesRawResponse xmlns="http://www.timelog.com/ws/tlp/v4_4">
      <GetEmployeesRawResult>
        <tlp:Errors xmlns:tlp="http://www.timelog.com/XML/Schema/tlp/v4_4">
          <tlp:Error>Access denied. Check siteCode, apiID, apiPassword and SSL settings</tlp:Error>
        </tlp:Errors>
      </GetEmployeesRawResult>
    </GetEmployeesRawResponse>
  </soap:Body>
</soap:Envelope>

Data and No rows are illustrative examples: the format follows the service's documented output, with made-up values (only one record shown). Access denied was recorded from a real call with wrong credentials (to GetCustomersShortList; every data method answers the same way).

Errors

The errors every method can return (access denied, operation failed, invalid request) are listed once in Responses and errors.

This method has no errors of its own beyond the shared ones.

Was this page helpful?