Simployer MIM-AD API

Modified on Fri, 4 Jul at 12:51 PM

Overview

This document describes the API for use with MIM or On-Premises Active Directory for customers who want to extract employee data and write back UPN and email.


MIM Integration



MIM is a solution that only offers scheduled jobs and will access an API endpoint at fixed times. The APIs are otherwise always available for queries or updates.

The proposed solution is to set up an API where MIM or other integration jobs can read personal data and update email addresses. The API will consist of two methods: ExportMIMData and ImportMIMData. A service provider will often prefer to extract all employees on each call. There is no need or functionality to transfer the entire organizational structure.


Mapping MIM – AD – Simployer

AD NameSimployer Field
companyEmployee in (Ansatt i)
departmentAffiliation (Tilhørighet)
employeeIDEmployee number (Ansattnummer)
employeeTypePersonnel category
givenNameFirst name (Fornavn)
lPostal code on department
managerImmediate manager (Nærmeste leder)
mobileMobile
physicalDeliveryOfficeNameDepartment name (Navn på avdeling)
postOfficeBoxAddress line 2 (Adr.linje 2) on department
postalCodePostal code on department
roomNumberField does not exist in size and value, but a “Size and Value” can be created in Simployer
streetAddressAddress line 1 (Adr.linje 1) on department
snLast name (Etternavn)
telephoneNumberMobile
titleJob title (Stillingsbenevnelse)
preferredLanguageLanguage (Språk)
Start date
Expire dateEnd date (Sluttdato)
TemplateTemplate, template user defined as group
emailEmail
UPNExternal ID
CustomField1
CustomField2
CustomField3


API

ExportMIMData
URL: https://simployermim.azure-api.net/MIMFunctions/ExportMIMData
Method: GET

Authentication
Basic auth with username and password.

Headers

KeyExample valueDescription
X-ITAS-FromUnitId3Unit
X-ITAS-UnitIdTypeInternalIdIdentifier type: DepartmentCode or InternalId
X-ITAS-IncludeSVCategory:customAttribute1SalaryType:customAttribute2
x-ITAS-PublicCustomerIdPublic customer id
x-ITAS-ApiKeyAPI key
Ocp-Apim-Subscription-KeySubscription key
Content-Typeapplication/json


Example response body
JSON array with person data:

json
CopyEdit
[ { "company": "Selskap AS", "department": "100", "employeeID": "55555555-5555-5555-5555-555555555555", "employeeNumber": "25", "employeetype": "Fast ansatt", "givenName": "Kari", "location": "1635", "manager": "Ola Hansen", "mobile": "98989898", "office": "Sarpsborg", "postOfficeBox": "PB 243", "postalCode": "1635", "roomNumber": "Etg. 2", "state": null, "streetAddress": "Kongens gate 2", "surname": "Hansen", "telephone": "98989898", "title": "Lærling", "countryCode": "NO", "preferredLanguage": null, "hireDate": "23.01.2018", "expireDate": "", "template": "Standard", "email": "kari@simployer.com", "adName": "kari@simployer.com", "customAttribute1": null, "customAttribute2": null, "customAttribute3": null } ]


ImportMIMData
URL: https://simployermim.azure-api.net/MIMFunctions/ImportMIMData
Method: POST

Authentication
Basic auth with username and password.

Headers

KeyExample valueDescription
Ocp-Apim-Subscription-KeySubscription key
Content-Typeapplication/json
X-ITAS-UpdateUserNameFalseSet to true to update user name with adName


Body
JSON array with MIM import data:

json
CopyEdit
[ { "employeeID": "55555555-5555-5555-5555-555555555555", "adName": "kari@simployer.com", "mail": "kari@simployer.com" } ]


Field description

FieldMax Length / FormatRequiredComment
employeeIDGUIDYes
adNameMax 100 charactersYes
mailMax 50 charactersYes


Simployer Customizations

The ExportMIMData method provides an export from Simployer of persons with job information. The most natural location in Simployer is to use the address at the unit level as the location when transferring to the service provider or AD. This means the organizational structure in Simployer must be updated with address information. The postal place represents the location. Location information can be used to control setups such as local printers.

Some service providers use template users to predefine a set of accesses. The suggested solution in Simployer is to create groups representing these template users. These groups can be linked directly to a person and/or to a job position. Some users will require cross-functional access, which will require separate templates.

Preferred language is used to set the default language for the user. In Simployer, this is the language field under account information.

Functionality to activate/deactivate persons can be controlled using the start and end date fields. In AD, there is an expire date which can be mapped to the end date in Simployer.


Prerequisites

  • Export extracts persons based on employee number

  • Address must be entered in the organization at the unit level

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article