Nepton Help Center

https://github.com/strom-capital/nepton-docs
Admin
Markdown mirror of the public Nepton Zendesk Help Center (support.nepton.com/hc), in Finnish and...
Tokens:343,822
Snippets:3,909
Trust Score:4.6
License:MIT
Update:4 months ago
Show doc for...
Tokens:
Raw
### Example Request for EnsureProjectsExistV2

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/360005783318-EnsureProjectsExistV2.md

This is an example of a SOAP request to the EnsureProjectsExistV2 API. It includes project details such as external identifiers, name, code, type, description, start date, and parent project.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Header/>
      <soapenv:Body>
        <tyo:ParametersForEnsureProjectsExistV2>
          <CallerAuthentication /> <!-- Authentication is required but is omitted from this example -->
          <ProjectList>
            <Project>
              <ExistingProjectIdentifier>
                <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ExistingProjectIdentifier>
              <ExternalIdentifier>
                <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ExternalIdentifier>
              <Name>Projekti X</Name>
              <Code>1000/9001</Code>
              <TypeInternalName>project_work</TypeInternalName>
              <Description>Lorem ipsum primis venenatis justo mollis fringilla lectus sociosqu nostra, vehicula nunc massa sodales habitasse duis</Description>
              <StartDate>2001-01-01</StartDate>
              <EndDate xsi:nil="true" />
              <ParentProjectIdentifier>
                <Identifier>45453ddd-f167-408b-9e75-6c419755caf8</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ParentProjectIdentifier>
            </Project>
          </ProjectList>
        </tyo:ParametersForEnsureProjectsExistV2>
      </soapenv:Body>
    </soapenv:Envelope>
```

--------------------------------

### Insert Standard Activity with Project Relations

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/27550371952925-InsertActivitiesV4.md

This example shows how to insert a standard work activity. It includes details like user personnel number, activity type, start time, and approver. It also demonstrates how to link the activity to projects using either an internal identifier or a project code, specifying the duration for each relation.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:tyo="http://tyoaika.tyoteho.fi">
      <soapenv:Header/>
      <soapenv:Body>
        <tyo:ParametersForInsertActivitiesV4>
          <CallerAuthentication /><!-- Authentication is required but is omitted from this example -->
          <ActivityList>
            <Activity>
              <UserPersonnelNumber>9001</UserPersonnelNumber>
              <ActivityTypeCode>201</ActivityTypeCode>
              <BeginDateTime>2021-01-19T08:00:00</BeginDateTime>
              <ApproverUserPersonnelNumber>9999</ApproverUserPersonnelNumber>
              <Comment>Hard work</Comment>
              <IsClockedEvent>true</IsClockedEvent>
              <ExternalIdentifiers>
                <ExternalIdentifier>
                  <Identifier>27ae3e08-bfa0-11eb-8529-0242ac130003</Identifier>
                  <IdentifierType>External</IdentifierType>
                </ExternalIdentifier>
              </ExternalIdentifiers>
              <RelatedProjects>
                <ActivityToProjectRelation>
                  <Id>1234567890</Id><!-- Refers to a project with Nepton internal identifier 1234567890 -->
                  <Duration>120</Duration>
                </ActivityToProjectRelation>
                <ActivityToProjectRelation>
                  <Code>ExampleProjectCode</Code><!-- Refers to a project with code ExampleProjectCode -->
                  <Duration>60</Duration>
                </ActivityToProjectRelation>
              </RelatedProjects>
            </Activity>
          </ActivityList>
        </tyo:ParametersForInsertActivitiesV4>
      </soapenv:Body>
    </soapenv:Envelope>
```

--------------------------------

### Example: Limit and Order Data

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/System-specific-person-imports/360014650697-Person-import-Sympa-API.md

This example demonstrates how to retrieve a specific number of people, ordered by last name, from the interface.

```URL
/?$orderby=LastName&$top=5
```

--------------------------------

### EnsureProjectsExistV4 Response Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36507754396573-EnsureProjectsExistV4.md

This snippet shows an example of the XML response returned by the EnsureProjectsExistV4 API method when successful.

```APIDOC
## EnsureProjectsExistV4

### Description
This API method is used to ensure that projects exist within the system. It returns detailed information about the status of each project processed.

### Method
SOAP

### Endpoint
(SOAP endpoint not specified in source)

### Request Body
(Request body details not specified in source)

### Response
#### Success Response (200 OK)
- **ResponseCode** (string) - The overall response code for the operation.
- **ResponseString** (string) - A message describing the overall outcome.
- **EnsureProjectsExistResultList** (list) - A list of results for each project processed.
  - **EnsureProjectsExistResult** (object) - Details for a single project.
    - **ResponseCode** (string) - The response code for this specific project.
    - **ResponseString** (string) - A message describing the outcome for this project.
    - **ProjectId** (string) - The unique identifier for the project.
    - **ProjectIdentifier** (object) - The identifier for the project.
      - **Identifier** (string) - The value of the identifier.
      - **IdentifierType** (string) - The type of the identifier.
    - **ProjectManagers** (list) - A list of project managers associated with the project.
      - **ProjectManager** (object) - Details of a project manager.
        - **UserId** (string) - The user ID of the project manager.
        - **UserName** (string) - The username of the project manager.
        - **PersonnelNumber** (string) - The personnel number of the project manager.
        - **PersonExternalIdentifier** (object) - The external identifier for the person.
          - **Identifier** (string) - The value of the external identifier.
          - **FieldName** (string) - The name of the field for the external identifier.

### Response Example
```xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <SOAP-ENV:Body>
    <tyo:ReturnValueForEnsureProjectsExistV4>
      <ResponseCode>1000</ResponseCode>
      <ResponseString>All clear. No errors.</ResponseString>
      <EnsureProjectsExistResultList>
        <EnsureProjectsExistResult>
          <ResponseCode>1000</ResponseCode>
          <ResponseString>All clear. No errors.</ResponseString>
          <ProjectId>76254</ProjectId>
          <ProjectIdentifier>
            <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
            <IdentifierType>ExternalIdentifier</IdentifierType>
          </ProjectIdentifier>
          <ProjectManagers>
            <ProjectManager>
              <UserId>09876543210</UserId>
              <UserName>Test User</UserName>
              <PersonnelNumber>27</PersonnelNumber>
              <PersonExternalIdentifier>
                <Identifier>MGR-010101</Identifier>
                <FieldName>ExternalIdentifier1</FieldName>
              </PersonExternalIdentifier>
            </ProjectManager>
            <ProjectManager>
              <UserId>1234567890</UserId>
              <UserName>Example Username</UserName>
              <PersonnelNumber>1274</PersonnelNumber>
              <PersonExternalIdentifier>
                <Identifier>MGR-67890</Identifier>
                <FieldName>ExternalIdentifier1</FieldName>
              </PersonExternalIdentifier>
            </ProjectManager>
            <ProjectManager>
              <UserId>0234567890</UserId>
              <UserName>Other example</UserName>
              <PersonnelNumber>12714</PersonnelNumber>
              <PersonExternalIdentifier>
                <Identifier>MGR-12345</Identifier>
                <FieldName>ExternalIdentifier1</FieldName>
              </PersonExternalIdentifier>
            </ProjectManager>
          </ProjectManagers>
        </EnsureProjectsExistResult>
      </EnsureProjectsExistResultList>
    </tyo:ReturnValueForEnsureProjectsExistV4>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
```
```

--------------------------------

### Example SQL Query for Netvisor Integration

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/Salary-systems/360007534058-Netvisor.md

An example SQL query demonstrating how to select user salary data, including personnel number as the employee ID, for integration with Netvisor.

```sql
SELECT UserSalaryData.*, SUM(UserSalaryData.Amount) As OverrideAmount, 
      UserData.Personnelnumber AS NetvisorFieldEmployeeId, 
      'number' AS NetvisorAttributeEmployeeIdType 
    FROM UserSalaryData 
    JOIN UserData ON (UserSalaryData.UserId = UserSalaryData.UserId)
    WHERE UserSalaryData.CompensationType = 'BasicTime'
```

--------------------------------

### Example API Response for ClearVisibleProjectsForUserV2

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36506225707677-ClearVisibleProjectsForUserV2.md

This is an example of a successful response from the ClearVisibleProjectsForUserV2 API call, indicating no errors and detailing the results for each cleared project.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ReturnValueForClearVisibleProjectsForUserV2>
      <ResponseCode>0</ResponseCode>
      <ResponseString>No errors</ResponseString>
      <ClearVisibleProjectsForUserResultList>
        <ClearVisibleProjectForUserResult>
          <ResponseCode>0</ResponseCode>
          <ResponseString>No errors</ResponseString>
          <UserId>1234</UserId>
          <Username>matti.meikalainen</Username>
          <PersonExternalIdentifier>
            <Identifier>EXP-12345</Identifier>
            <FieldName>ExternalIdentifier1</FieldName>
          </PersonExternalIdentifier>
        </ClearVisibleProjectForUserResult>
      </ClearVisibleProjectsForUserResultList>
    </tyo:ReturnValueForClearVisibleProjectsForUserV2>
  </soapenv:Body>
</soapenv:Envelope>
```

--------------------------------

### SetVisibleProjectsForUserV3 Response Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36513542448925-SetVisibleProjectsForUserV3.md

This is an example of a SOAP response from the SetVisibleProjectsForUserV3 API. It details the outcome for each project visibility setting operation.

```xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://tyoaika.tyoteho.fi"> 
  <SOAP-ENV:Body> 
    <ns1:ReturnValueForSetVisibleProjectsForUserV3> 
      <ResponseCode>1000</ResponseCode> 
      <ResponseString>All clear. No errors.</ResponseString> 
      <SetVisibleProjectsForUserResultList> 
        <SetVisibleProjectsForUserResult> 
          <ResponseCode>1000</ResponseCode> 
          <ResponseString>All clear. No errors.</ResponseString> 
          <ProjectId>76254</ProjectId> 
          <ProjectCode>1000/9001</ProjectCode> 
          <ProjectIdentifier> 
            <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier> 
            <IdentifierType>ExternalIdentifier</IdentifierType> 
          </ProjectIdentifier> 
          <UserId>1234</UserId> 
          <Username>matti.meikäläinen</Username> 
          <PersonnelNumber>9001</PersonnelNumber> 
        </SetVisibleProjectsForUserResult> 
      </SetVisibleProjectsForUserResultList> 
    </ns1:ReturnValueForSetVisibleProjectsForUserV3> 
  </SOAP-ENV:Body> 
</SOAP-ENV:Envelope>
```

--------------------------------

### GetProjectsV2 Request Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/6904062030621-GetProjectsV2.md

This example demonstrates how to structure a SOAP request to the GetProjectsV2 API to filter projects by their external identifiers. Authentication details are omitted for brevity.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ParametersForGetProjectsV2>
      <CallerAuthentication /> <!-- Authentication is required but is left out in this example -->
      <FilterByExternalIdentifiers>external-12345</FilterByExternalIdentifiers>
    </tyo:ParametersForGetProjectsV2>
  </soapenv:Body>
</soapenv:Envelope>
```

--------------------------------

### SOAP Response Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36510325765533-InsertActivitiesV5.md

This is an example of a successful response from the InsertActivitiesV5 API. It includes response codes, descriptions, and details of the added activity.

```xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"xmlns:tyo="http://tyoaika.tyoteho.fi">
      <SOAP-ENV:Body>
        <tyo:ReturnValueForInsertActivitiesV5>
          <ResponseCode>1000</ResponseCode>
          <ResponseString>All clear. No errors.</ResponseString>
          <ActivityList>
            <Activity>
              <Id>12345678</Id>
              <ExternalIdentifiers>
                <ExternalIdentifier>
                  <Identifier>27ae3e08-bfa0-11eb-8529-0242ac130003</Identifier>
                  <IdentifierType>External</IdentifierType>
                </ExternalIdentifier>
              </ExternalIdentifiers>
              <Success>true</Success>
            </Activity>
          </ActivityList>
        </tyo:ReturnValueForInsertActivitiesV5>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
```

--------------------------------

### SetVisibleProjectsForUserV3 Request Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36513542448925-SetVisibleProjectsForUserV3.md

This is an example of a SOAP request to set visible projects for a user. It includes project identifiers and personnel numbers. Authentication is required but omitted for brevity.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi"> 
  <soapenv:Header/> 
  <soapenv:Body> 
    <tyo:ParametersForSetVisibleProjectsForUserV3> 
      <CallerAuthentication /> <!-- Autentikoituminen vaaditaan, mutta on jätetty tässä esimerkissä pois --> 
      <SetVisibleProjectsForUserList> 
        <SetVisibleProjectForUser> 
          <ProjectIdentifier> 
            <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier> 
            <IdentifierType>ExternalIdentifier</IdentifierType> 
          </ProjectIdentifier> 
          <PersonnelNumber>9001</PersonnelNumber> 
          <ProjectVisible>true</ProjectVisible> 
        </SetVisibleProjectForUser> 
        <SetVisibleProjectForUser> 
          <ProjectCode>PRJ-001</ProjectCode> 
          <PersonExternalIdentifier> 
            <Identifier>EMP-12345</Identifier> 
            <FieldName>ExternalIdentifier1</FieldName> 
          </PersonExternalIdentifier> 
        </SetVisibleProjectForUser> 
      </SetVisibleProjectsForUserList> 
    </tyo:ParametersForSetVisibleProjectsForUserV3> 
  </soapenv:Body> 
</soapenv:Envelope>
```

--------------------------------

### SD Worx Export Data Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/Salary-systems/28022676814109-SD-Worx-difference-data.md

This example demonstrates the format of exported data for an 8-hour work event, excluding lunch, as it would appear for SD Worx integration.

```text
    1234567-1;219354;10;01.01.2025;1000;3,50;;;02.06.2025;05.06.2025;  
    1234567-1;219354;10;01.01.2025;1000;4,00;;;05.06.2025;05.06.2025;
```

--------------------------------

### JSON Person Import Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/360003762577-Person-Import.md

Example of a JSON file structure for person import. The 'ImportUserData' key contains an array of person objects, each with various fields.

```json
{
   "ImportUserData":[
      {
         "Henkilönumero":"123456",
         "Etunimi":"Matti",
         "Sukunimi":"Esimerkki",
         "Ammattinimike":"Suunnittelija",
         "Työsuhteen alkupäivä":"01.04.2019",
         "Työsuhteen päättymispäivä":""
      },
      {
         "Henkilönumero":"23456",
         "Etunimi":"Juha",
         "Sukunimi":"Esimerkki",
         "Työsuhteen alkupäivä":"01.07.2022",
         "Työsuhteen päättymispäivä":null
      }
   ]
}
```

--------------------------------

### Get Accrual Values for User Request

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/6913825701277-GetAccrualValuesForUser.md

Example of a SOAP request to retrieve accrual values for a specific user and date. Authentication details are omitted for brevity.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ParametersForGetAccrualValuesForUser>
      <CallerAuthentication /> <!-- Authentication is needed but not shown in this example -->
      <UserPersonnelNumber>2345</UserPersonnelNumber>
      <SalaryDate>2020-01-01</SalaryDate>
    </tyo:ParametersForGetAccrualValuesForUser>
  </soapenv:Body>
</soapenv:Envelope>
```

--------------------------------

### BeginActivityV2

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/6869562936221-BeginActivityV2.md

This API method allows you to start an activity in the Nepton system. It requires authentication and specifies the activity type, start time, and optional details like terminal ID, comments, and related projects.

```APIDOC
## BeginActivityV2

### Description
This API method allows you to start an activity in the Nepton system. It requires authentication and specifies the activity type, start time, and optional details like terminal ID, comments, and related projects.

### Method
POST (SOAP)

### Endpoint
(SOAP endpoint not specified in source, assumed to be a service endpoint)

### Parameters
#### Request Body (XML Structure for ParametersForBeginActivityV2)
- **CallerAuthentication** (XML element) - Required - More information about authentications [here](<https://support.nepton.com/hc/en-gb/articles/360019983978>).
- **ActivityTypeId** (integer) - Required - The Nepton identifier of the event type to be started. The list of event types can be read via the API. More info [here](<https://support.nepton.com/hc/en-gb/articles/360019840217>).
- **BeginDateTime** (datetime) - Optional - The start date and time of the event type to be started. Data given in form `VVVV-KK-PPTHH:MM:SS`, for example`2021-02-18T12:30:00`. If this data is not given, the event will start at current time.
- **EndDateTime** (datetime) - Optional - The end date and time of the event. Data given in format `VVVV-KK-PPTHH:MM:SS`, esimerkiksi `2021-02-18T12:30:00`. Not mandatory. The event can be ended via another method.
- **TerminalId** (integer) - Optional - Terminal identifier. Any identifier can be used, as long as the identifiers are integers.
- **Comment** (string) - Optional - Any comments for events.
- **OvertimeBasePartTargetedTo** (string) - Optional - Accrual, where overtime base part is being directed to. See possible values [here](<https://support.nepton.com/hc/en-gb/articles/6904407712413>).
- **OvertimeIncrementPartTargetedTo** (string) - Optional - Accrual, where overtime increment part is being directed to. See possible values [here](<https://support.nepton.com/hc/en-gb/articles/6904407712413>).
- **RelatedProjects** (XML element) - Optional - Projects to be registered for the event.
  - **ActivityToProjectRelation** (XML element) - 0..n
    - **Id** (integer) - Optional - The unique identifier of the project in Nepton. The unique identifier of the project or project code must be provided.
    - **Duration** (integer) - Optional - Project duration in minutes.
    - **Name** (string) - Optional - Project name. Data is not used.
    - **Code** (string) - Optional - Project code. The unique identifier of the project or project code must be provided.
- **WorkIncrements** (XML element) - Optional - Supplements to be added to the event.
  - **WorkIncrement** (XML element) - 0..n
    - **Index** (integer) - Required - Index of supplement
    - **Value** (decimal) - Required - Supplement value in minutes, units or decimals.
- **ExternalIdentifiers** (XML element) - Optional - External identifiers given to the event
  - **ExternalIdentifier** (XML element) - 1..n
    - **Identifier** (string) - Required - External identifier
    - **IdentifierType** (string) - Required - Type of external identifier. The only supported type at the moment is `External`.

### Request Example
```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ParametersForBeginActivityV2>
      <CallerAuthentication /> <!-- Authentication is needed, but left out on this example --> 
      <ActivityTypeId>1</ActivityTypeId>
      <BeginDateTime>2021-05-28T07:35:34</BeginDateTime>
      <TerminalId>418</TerminalId>
      <ExternalIdentifiers>
        <ExternalIdentifier>
          <Identifier>ae2f6c97-104f-49e4-9cff-70951f00234e</Identifier>
          <IdentifierType>External</IdentifierType>
        </ExternalIdentifier>
      </ExternalIdentifiers>
    </tyo:ParametersForBeginActivityV2>
  </soapenv:Body>
</soapenv:Envelope>
```

### Response
(Response details not provided in the source text)
```

--------------------------------

### Get Accrual Values for User Response

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/6913825701277-GetAccrualValuesForUser.md

Example of a SOAP response from the GetAccrualValuesForUser API, showing accrual details including internal name, display name, amount, and change amount.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ReturnValueForGetAccrualValuesForUser>
      <ResponseCode>?</ResponseCode>
      <ResponseString>?</ResponseString>
      <AccrualList>
        <Accrual>
          <InternalName>bank</InternalName>
          <Name>pankki</Name>
          <Amount>18</Amount>
          <ChangeAmount>10</ChangeAmount>
        </Accrual>
      </AccrualList>
    </tyo:ReturnValueForGetAccrualValuesForUser>
  </soapenv:Body>
</soapenv:Envelope>
```

--------------------------------

### InsertActivitiesV3 - Standard Activity

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/6788985086621-InsertActivitiesV3.md

This example demonstrates how to insert a standard work activity using the InsertActivitiesV3 API. It includes details such as user personnel number, activity type code, start time, approver, comment, and related project information.

```APIDOC
## POST /InsertActivitiesV3

### Description
Inserts a standard work activity into the system. This includes details like user, activity type, time, and project associations.

### Method
POST

### Endpoint
/InsertActivitiesV3

### Request Body
- **CallerAuthentication** (string) - Required - Authentication credentials.
- **ActivityList** (object) - Required - A list of activities to insert.
  - **Activity** (object) - Represents a single activity.
    - **UserPersonnelNumber** (string) - Required - The personnel number of the user performing the activity.
    - **ActivityTypeCode** (string) - Required - The code representing the type of activity.
    - **BeginDateTime** (string) - Required - The start date and time of the activity (ISO 8601 format).
    - **ApproverUserPersonnelNumber** (string) - Required - The personnel number of the approver for this activity.
    - **Comment** (string) - Optional - A comment associated with the activity.
    - **IsClockedEvent** (boolean) - Optional - Indicates if this is a clocked event.
    - **ExternalIdentifiers** (object) - Optional - A list of external identifiers for the activity.
      - **ExternalIdentifier** (object) - Represents an external identifier.
        - **Identifier** (string) - Required - The identifier value.
        - **IdentifierType** (string) - Required - The type of the identifier.
    - **RelatedProjects** (object) - Optional - Projects related to this activity.
      - **ActivityToProjectRelation** (object) - Represents a relation to a project.
        - **Id** (string) - Required if Code is not present - The internal identifier of the project.
        - **Code** (string) - Required if Id is not present - The code of the project.
        - **Duration** (string) - Required - The duration spent on the project in minutes.

### Request Example
```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ParametersForInsertActivitiesV3>
      <CallerAuthentication /><!-- Authentication is required but is omitted from this example -->
      <ActivityList>
        <Activity>
          <UserPersonnelNumber>9001</UserPersonnelNumber>
          <ActivityTypeCode>201</ActivityTypeCode>
          <BeginDateTime>2021-01-19T08:00:00</BeginDateTime>
          <ApproverUserPersonnelNumber>9999</ApproverUserPersonnelNumber>
          <Comment>Hard work</Comment>
          <IsClockedEvent>true</IsClockedEvent>
          <ExternalIdentifiers>
            <ExternalIdentifier>
              <Identifier>27ae3e08-bfa0-11eb-8529-0242ac130003</Identifier>
              <IdentifierType>External</IdentifierType>
            </ExternalIdentifier>
          </ExternalIdentifiers>
          <RelatedProjects>
            <ActivityToProjectRelation>
              <Id>1234567890</Id><!-- Refers to a project with Nepton internal identifier 1234567890 -->
              <Duration>120</Duration>
            </ActivityToProjectRelation>
            <ActivityToProjectRelation>
              <Code>ExampleProjectCode</Code><!-- Refers to a project with code ExampleProjectCode -->
              <Duration>60</Duration>
            </ActivityToProjectRelation>
          </RelatedProjects>
        </Activity>
      </ActivityList>
    </tyo:ParametersForInsertActivitiesV3>
  </soapenv:Body>
</soapenv:Envelope>
```

### Response
(Success and error response details not provided in source)
```

--------------------------------

### JSON Example with Validity Dates

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/Field-validities-in-person-imports/360015842238-Person-imports-with-validity-start-and-end-information.md

This JSON snippet demonstrates importing a 'Job Title' field with validity start and end dates. The 'First Name' and 'Last Name' fields are imported without validity information, following a different import method.

```json
"Henkilö": [
{
"Henkilönumero": "1234",
"Etunimi": "Esa",
"Sukunimi": "Esimerkki",
"Ammattinimike": [
{
"Voimassa alkaen": "2000-01-01",
"Voimassa päättyen": "2020-11-30",
"Arvo": "Myyjä"
},
{
"Voimassa alkaen": "2021-01-01",
"Voimassa päättyen": null,
"Arvo": "Myyntipäällikkö"
}
]
}
]
```

--------------------------------

### InsertActivitiesV4 - Standard Activity

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/27550371952925-InsertActivitiesV4.md

This example demonstrates how to insert a standard work activity using the InsertActivitiesV4 API. It includes details like user personnel number, activity type code, start time, approver, comments, and related project information.

```APIDOC
## POST /InsertActivitiesV4

### Description
Inserts a standard work activity into the system. This includes details about the user, the activity itself, and any associated projects.

### Method
POST

### Endpoint
/InsertActivitiesV4

### Request Body
- **CallerAuthentication** (string) - Required - Authentication token for the caller.
- **ActivityList** (object) - Required - A list of activities to insert.
  - **Activity** (object) - Represents a single activity.
    - **UserPersonnelNumber** (string) - Required - The personnel number of the user performing the activity.
    - **ActivityTypeCode** (string) - Required - The type code of the activity.
    - **BeginDateTime** (string) - Required - The start date and time of the activity (ISO 8601 format).
    - **ApproverUserPersonnelNumber** (string) - Required - The personnel number of the approver.
    - **Comment** (string) - Optional - A comment about the activity.
    - **IsClockedEvent** (boolean) - Optional - Indicates if this is a clocked event.
    - **ExternalIdentifiers** (object) - Optional - A list of external identifiers for the activity.
      - **ExternalIdentifier** (object) - Represents an external identifier.
        - **Identifier** (string) - Required - The identifier value.
        - **IdentifierType** (string) - Required - The type of the identifier.
    - **RelatedProjects** (object) - Optional - A list of projects related to the activity.
      - **ActivityToProjectRelation** (object) - Represents a relation to a project.
        - **Id** (string) - Required - The internal identifier of the project.
        - **Duration** (string) - Required - The duration spent on the project in minutes.
        - **Code** (string) - Required - The code of the project (alternative to Id).

### Request Example
```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"xmlns:tyo="http://tyoaika.tyoteho.fi">
  <soapenv:Header/>
  <soapenv:Body>
    <tyo:ParametersForInsertActivitiesV4>
      <CallerAuthentication />
      <ActivityList>
        <Activity>
          <UserPersonnelNumber>9001</UserPersonnelNumber>
          <ActivityTypeCode>201</ActivityTypeCode>
          <BeginDateTime>2021-01-19T08:00:00</BeginDateTime>
          <ApproverUserPersonnelNumber>9999</ApproverUserPersonnelNumber>
          <Comment>Hard work</Comment>
          <IsClockedEvent>true</IsClockedEvent>
          <ExternalIdentifiers>
            <ExternalIdentifier>
              <Identifier>27ae3e08-bfa0-11eb-8529-0242ac130003</Identifier>
              <IdentifierType>External</IdentifierType>
            </ExternalIdentifier>
          </ExternalIdentifiers>
          <RelatedProjects>
            <ActivityToProjectRelation>
              <Id>1234567890</Id>
              <Duration>120</Duration>
            </ActivityToProjectRelation>
            <ActivityToProjectRelation>
              <Code>ExampleProjectCode</Code>
              <Duration>60</Duration>
            </ActivityToProjectRelation>
          </RelatedProjects>
        </Activity>
      </ActivityList>
    </tyo:ParametersForInsertActivitiesV4>
  </soapenv:Body>
</soapenv:Envelope>
```

### Response
(Response details not provided in the source text)

```

--------------------------------

### Example of Set Data in Netvisor

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/Salary-systems/360007534058-Netvisor.md

This XML structure represents an example of data that can be set for a workday in Netvisor. It includes details like date, employee identifier, and work time information.

```XML
<root>
      <workday>
        <date format="ansi" method="replace">2016-03-14</date>
        <employeeidentifier type="personalidentificationnumber">111111-1111</employeeidentifier>
        <workdaytime>
          <starttimeofday>12:30</starttimeofday>
          <endtimeofday>16:00</endtimeofday>
          <breaktime type="minutes">0</breaktime>
          <collectorratio type="number">123</collectorratio>
          <acceptancestatus>confirmed</acceptancestatus>
          <description>Iltapäivä</description>
        </workdaytime>
      </workday>
    </root>
```

--------------------------------

### Null StartDate Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/360005783318-EnsureProjectsExistV2.md

Demonstrates how to represent a null StartDate in the XML request.

```xml
<StartDate xsi:nil="true" />
```

--------------------------------

### Mepco Integration File Example (With Optional Columns)

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/Events/360003773337-Mepco-scheduled-event-import.md

This snippet demonstrates the format of a Mepco integration file including optional columns for time and duration. Pay attention to the correct placement and formatting of these optional fields.

```text
Esimerkki;Erika;1109;24.01.2014;25.01.2014;06.1;L;;;;;
Hollola;Heidi;2404;01.10.2014;01.10.2014;08.0;P;01.10.2014;08:00;10:00;10:00;
Hollola;Heidi;2404;22.09.2014;26.09.2014;08.0;P;;06:00;;;04:00
```

--------------------------------

### Content-Length Header Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/8042662966429-Export-HR-data-to-a-REST-API-endpoint.md

This is an example of a Content-Length header, specifying the size of the request body in bytes.

```http
Content-Length: 3909
```

--------------------------------

### Example EnsureProjectsExistV4 Request

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/36507754396573-EnsureProjectsExistV4.md

This is an example SOAP request for the EnsureProjectsExistV4 API. It demonstrates how to structure the XML payload to include project details such as identifiers, names, codes, and project managers. Authentication details are omitted for brevity.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Header/>
      <soapenv:Body>
        <tyo:ParametersForEnsureProjectsExistV3>
          <CallerAuthentication /> <!-- Authentication is required but is omitted from this example -->
          <ProjectList>
            <Project>
              <ExistingProjectIdentifier>
                <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ExistingProjectIdentifier>
              <ExternalIdentifier>
                <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ExternalIdentifier>
              <Name>Projekti X</Name>
              <Code>1000/9001</Code>
              <TypeInternalName>project_work</TypeInternalName>
              <Description>Lorem ipsum primis venenatis justo mollis fringilla lectus sociosqu nostra, vehicula nunc massa sodales habitasse duis</Description>
              <StartDate>2001-01-01</StartDate>
              <EndDate xsi:nil="true" />
              <ParentProjectIdentifier>
                <Identifier>45453ddd-f167-408b-9e75-6c419755caf8</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ParentProjectIdentifier>
              <ProjectManagers>
                <RemoveOthers>true</RemoveOthers>
                <ProjectManager>
                  <PersonnelNumber>27</PersonnelNumber>
                </ProjectManager>
                <ProjectManager>
                  <UserName>Example Username</PersonnelNumber>
                </ProjectManager>
                <ProjectManager>
                  <PersonExternalIdentifier>
                    <Identifier>MGR-12345</Identifier>
                    <FieldName>ExternalIdentifier1</FieldName>
                  </PersonExternalIdentifier>
                </ProjectManager>
              </ProjectManagers>
            </Project>
          </ProjectList>
        </tyo:ParametersForEnsureProjectsExistV3>
      </soapenv:Body>
    </soapenv:Envelope>
```

--------------------------------

### Rule Commands for Late Work Start

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Worktime-calculations-and-management/Setting-exceptions/360002560677-Configure-exceptions-to-settings.md

These rule commands specify conditions for workdays with a specific event type, starting at or after 22:00 and before 24:01. The 24:01 value in WORK-DAY-BEGINS-BEFORE is used to include midnight and work starting on the next day.

```rule
[WORK-DAY-HAS-ANY-OF-EVENT-TYPES|1] 
    [WORK-DAY-BEGINS-AFTER|22:00] 
    [WORK-DAY-BEGINS-BEFORE|24:01]
```

--------------------------------

### 100-Continue Expect Header

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/8042662966429-Export-HR-data-to-a-REST-API-endpoint.md

This example shows the headers sent in an initial request to check server readiness before sending the full data payload. It includes the Content-Length and the Expect: 100-continue headers.

```http
Content-Length: 25959
Expect: 100-continue
```

--------------------------------

### Rule Commands for Early Work Start

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Worktime-calculations-and-management/Setting-exceptions/360002560677-Configure-exceptions-to-settings.md

These rule commands define conditions for when a workday has a specific event type and starts within a given time frame. Use WORK-DAY-BEGINS-BEFORE with a value of 22:01 to include work starting at or before 22:00.

```rule
[WORK-DAY-HAS-ANY-OF-EVENT-TYPES|1] 
    [WORK-DAY-BEGINS-AFTER|00:00] 
    [WORK-DAY-BEGINS-BEFORE|22:01]
```

--------------------------------

### GetUnits SOAP Message Example

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/HR-API/4406441875089-Authentication-in-HR-API.md

This example demonstrates how to authenticate and make a GetUnits request using a SOAP message.

```APIDOC
## POST https://go.nepton.com/API/SOAPWebService.asmx

### Description
This endpoint retrieves units from the HR API. Authentication requires specific credentials tied to a user and the deployment.

### Method
POST

### Endpoint
https://go.nepton.com/API/SOAPWebService.asmx

### Headers
- Content-Type: text/xml; charset=utf-8

### Parameters
#### Request Body
- **Username** (string) - Required - The username of a person configured in the Nepton service.
- **UserPassword** (string) - Required - The password of the above person. Note: Password cannot end with '&'.
- **DeploymentId** (string) - Required - A numeric value identifying your working community.
- **WebServicePassword** (string) - Required - A password related to the working community data.
- **IncludeDeletedUnits** (boolean) - Optional - Specifies whether to include deleted units.

### Request Example
```xml
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetUnits xmlns="http://tempuri.org/">
      <Request>
        <Username>Integration Account</Username>
        <UserPassword>e8bc7c00-17c8-4802-8962-c77e1071116c</UserPassword>
        <DeploymentId>285057</DeploymentId>
        <WebServicePassword>060b20fe-cd2a-4629-bdc5-7b896a1cebc6</WebServicePassword>
        <IncludeDeletedUnits>false</IncludeDeletedUnits>
      </Request>
    </GetUnits>
  </soap:Body>
</soap:Envelope>
```

### Response
#### Success Response (200)
- The response will contain a list of units based on the request parameters.

#### Response Example
(Response structure not explicitly defined in source, but would typically be a SOAP response containing unit data.)
```

--------------------------------

### JSON Example for New Person Import (12.12.2019)

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/HR-data/Field-validities-in-person-imports/360015842238-Person-imports-with-validity-start-and-end-information.md

This JSON example shows the data to be imported for a new person on 12.12.2019, including 'Job Title' with validity dates and 'Unit' with a validity period. It illustrates how validity-supported fields and non-supported fields are handled.

```json
"Henkilö": [
{
"Henkilönumero": "1234",
"Etunimi": "Esa",
"Sukunimi": "Esimerkki",
"Ammattinimike": [
{
"Voimassa alkaen": "2000-01-01",
"Voimassa päättyen": "2020-11-30",
"Arvo": "Myyjä"
},
{
"Voimassa alkaen": "2021-01-01",
"Voimassa päättyen": null,
"Arvo": "Myyntipäällikkö"
}
],
"Yksiköt": [
{
"Voimassa alkaen": "2000-01-01",
"Voimassa päättyen": "2020-12-31",
"Arvo": "Myynti"
}
]
}
]
```

--------------------------------

### SQL Clause for Late Work Start Exception

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Worktime-calculations-and-management/Setting-exceptions/360002560677-Configure-exceptions-to-settings.md

This SQL clause targets events with activity type code 1, where the start time is between 22:00 and 24:00 on the salary rendering date. This is useful for exceptions related to work starting late in the day.

```sql
FROM
      UserEventData
    WHERE
      ActivityTypeCode = 1
      AND StartDateTime >= :SalaryRenderingDate || ' ' || '22:00'
      AND StartDateTime <= :SalaryRenderingDate || ' ' || '24:00'
```

--------------------------------

### Example SOAP Call for RunIntegrationRulesetV2

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/360014449458-RunIntegrationRulesetV2.md

This snippet demonstrates the structure of a SOAP envelope for calling the RunIntegrationRulesetV2 API. It includes placeholders for authentication, ruleset name, date filters, and user filters. Authentication is required but omitted in this example.

```xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
      <soapenv:Header/>
      <soapenv:Body>
        <tyo:ParametersForRunIntegrationRulesetV2>
          <CallerAuthentication /> <!-- Authentication is required, but omitted in this example -->
          <IntegrationRulesetName>?</IntegrationRulesetName>
          <FilterPeriodBeginDate>?</FilterPeriodBeginDate>
          <FilterPeriodEndDate>?</FilterPeriodEndDate>
          <FilterByUsers> <!-- All 4 persons are retrieved, 2 matches with usernames and 2 matches with personnel numbers -->
            <Username>Matti Meikäläinen</Username>
            <Username>Maija Mehiläinen</Username>
            <PersonnelNumber>9001</PersonnelNumber>
            <PersonnelNumber>9002</PersonnelNumber>
          </FilterByUsers>
          <ReturnFormat>formatDefinedInRulesetSettings</ReturnFormat>
        </tyo:ParametersForRunIntegrationRulesetV2>
      </soapenv:Body>
    </soapenv:Envelope>
```

--------------------------------

### Example Response for EnsureProjectsExistV2

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/API/Example-APIs-and-method-descriptions/360005783318-EnsureProjectsExistV2.md

This is an example of a successful SOAP response from the EnsureProjectsExistV2 API. It includes response codes and details for the handled project, such as its Nepton ProjectId and the identifier that was sent in the request.

```xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tyo="http://tyoaika.tyoteho.fi">
      <SOAP-ENV:Body>
        <tyo:ReturnValueForEnsureProjectsExistV2>
          <ResponseCode>1000</ResponseCode>
          <ResponseString>All clear. No errors.</ResponseString>
          <EnsureProjectsExistResultList>
            <EnsureProjectsExistResult>
              <ResponseCode>1000</ResponseCode>
              <ResponseString>All clear. No errors.</ResponseString>
              <ProjectId>76254</ProjectId>
              <ProjectIdentifier>
                <Identifier>4a78611d-4a00-4c4a-a987-865664d732ce</Identifier>
                <IdentifierType>ExternalIdentifier</IdentifierType>
              </ProjectIdentifier>
            </EnsureProjectsExistResult>
          </EnsureProjectsExistResultList>
        </tyo:ReturnValueForEnsureProjectsExistV2>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
```

--------------------------------

### Mepco Integration File Example (Without Optional Columns)

Source: https://github.com/strom-capital/nepton-docs/blob/main/en-gb/Support/Integration/Events/360003773337-Mepco-scheduled-event-import.md

This snippet shows the format of a Mepco integration file when optional columns are not used. Ensure the data adheres to the specified field order and date/code formats.

```text
Esimerkki;Erika;1109;24.01.2014;24.01.2014;06.1;L;
Hollola;Heidi;2404;01.10.2014;03.10.2014;08.0;P;
Hollola;Heidi;2404;22.09.2014;26.09.2014;08.0;P;
Hollola;Heidi;2404;22.10.2014;26.10.2014;010.3;P;
Hollola;Heidi;2404;03.11.2014;05.11.2014;04.3;P;
Hollola;Heidi;2404;06.11.2014;06.11.2014;06.6;P;06.11.2014
```
Tokens:
Raw