Mijn Communities
Log in of maak account aan

om een gepersonaliseerde navigatie te krijgen.

Help

Kennisbank

Sorteren op:
I would like to start using the File API. Which are the first steps? Create an account To use the File API, you must register and create an account in the developer portal. An account is quick to set up and is free of charge. You only need your phone and company address to register. To register and create an account: 1. Click   Create an account   . 2. Enter your details. (Please register with your company email). 3. You will receive an SMS on your mobile to confirm. Create an application After login, you can go to   Your Apps   and see all applications you have access to. There you will be able to create a Sandbox App for File API and retrieve the crendentials (A pi Key, Secret key).    By default, the sandbox applications are authorized to TenantId: sandbox and to the Sandbox File Types. With the below sandbox file types you will be able to test how to upload and download files using File API.  Business Type Id Name Authorization 7100 File API Sandbox Uploads Publisher 7101 File API Sandbox Downloads Subscriber   Once your integration is ready, contact your API consultant or account manager to switch your Application from Sandbox to PROD. If multiple subscribers need the same file, wouldn’t the current setup of the API poses the risk that subscriber A (supplier system A) downloads and deletes a file of this type even though also subscribers B and C also require this file for their systems? The storage is unique and the files will be stored only once, no matter whether the same file is consumed by many subscribers. Each subscriber will receive a logical reference for the file. That means that if Subscriber A downloads the file, only the logical reference of the file for Subscriber A will be set as downloaded and not the logical references of Subscriber B and C.   When the files will be physically deleted from Storage? The files will be physically deleted from Storage automatically after the retention period expires (1 month) Will it be possible to request a list of files, filtered based on businessType/id and/or uploadDate?  Please visit our documentation. Section “search for files”   Can we use the API to upload DPIA100 files as well, or should our customers stick to the manual upload process? The File API can be used to upload files as well. Once the DPIA100 files are uploaded, they will be downloaded and imported in Beaufort.
Volledig artikel weergeven
17-01-2022 19:48 (Bijgewerkt op 17-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 4 Weergaven
The File API allows you to download or upload files directly from Youforce, over HTTPS using the tool of your choice.    This API is controlled available and has consumption limitations. See   API statuses   Authentication The File API is based on OAuth 2.0. Every API consumer system will be provisioned in our API Gateway as a Client Application (App). Client ID and Client Secret will be provided to be used by Apps as credentials. Thus, Apps will be able then to authenticate and get an access token (JWT) within the response payload. Subsequent requests authorization will be based on that access token previously retrieved.   Tenant Authorization Client Applications need to be authorized to the corresponding Tenant (HR Core Client) in order to consume the API. By default, the applications are authorized to TenantId:   sandbox.   File Type Authorization The files which are related to the same “business” are functionally grouped in File types called   Business types. Business Types are represented by an integer called Business Type Id. Client applications (apps) need to be authorized as publisher or subscriber of business types Publisher is an application that uploads files to be consumed for other subscribers Subscriber is an application that downloads the files provided by other publishers. By default, the client Apps are authorized to the Sandbox File Types.   Supported File Types The File API has been designed to support a specific set of use cases. This may be extended over time, based on customer feedback. See list of Supported File Types   Samples Here is an example of downloading a file using   curl, available on most operating systems:  curl.exe   https://api.raet.com/mft/v1.0/files/%fileid%?role=subscriber  ^ --header "Authorization:   Bearer eyJhbGciOiJSUzI1NiIs... "   ^ --header "x-raet-tenant-id:   1234567 " ^ --header "Accept: application/octet-stream"    ^ --output   @C:\Youforce\somefile.xml   Complete examples for curl (Batch), Powershell and .Net can be found on Github.  Getting started See here to get started  
Volledig artikel weergeven
17-01-2022 19:12 (Bijgewerkt op 17-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 2 Weergaven
  General Access to the Visma|Raet support desk When Partner first starts using the Domain API’s, Visma|Raet will create one end-user (hereinafter: Administrator) for Partner, who is given access to the Ticket system of Visma|Raet. An Administrator is an authorized person by Partner who uses the Domain API’s and subsequently is able to create new Administrators.  The Visma|Raet Ticket system is accessible through this link: Log Support Ticket Service Support Questions about the functioning of Domain API’s s are answered by Visma| Raet’s Service Center. We also process reports about malfunctions and deal with it adequately and ensure proper feedback. We offer these services to the registered, professional contact persons of Partner. The designated contact persons of Partner, are able to report detected incidents to Visma Raet’s Service Center. This is possible via accessing the Visma|Raet Ticket system.  In the case of escalation, you can contact us by telephone  The ticket system of Visma|Raet grants access and information about the progress of submitted questions and the offered solutions. Contact persons are during the support process able to add information and react to the offered solutions by Visma|Raet. Access by telephone of the Service Center  Access by telephone of the Service Center is meant for those situations where direct contact is needed to provide a solution or in case of escalation. The Service Center can be reached by telephone on workdays between 8:00 am and 6:00 pm.  We kindly ask you to enter your partner number and to choose between the Service on which the question is related to. Our Stand-by Service can be reached by telephone outside work hours, for reports with respect to the availability of the Domain APIs. The Stand-by Service is available on workdays between 6:00 am and 8:00 am and between 6:00 pm and 10:00 pm and during weekends between 6:00 am and 10:00 pm.   Note: The Stand-by Service is only for reports on malfunctions in the availability of the Domain API’s applications and is not meant for substantive questions or for reporting other malfunctions.  FAQ Who can get support? Partners only. See   How to become an Access Partner How can I log a ticket on an API on login? You will receive instructions for this as part of your access partner contract. How long does it take before my ticket is picked up? Visma | Raet applies four Support Level Codes to give the right priority to the malfunction and the corresponding response time. The distinction in Support Level Codes is based on the type, severity, the corresponding initial response time and the expected recovery time of the reported malfunction.  Code Meaning Description 1 High The malfunction has a far-reached and immediate effect on the activities in the organization of the customer: activities cannot continue. There is no alternative solution that offers similar results.  2 Medium The malfunction has a significant effect on the activities in the organization of the customer: An alternative solution is available, whether or not with some limitations. 3 Low The malfunction has limited or no effect on the activities in the organization of the customer The following resolution times relate to the Service Level Code, depending on the Service Code Meaning Maximum duration 1 High Solution by means of a workaround 90% within 24 hours 100% within 48 hours Structural solution: Within 30 calendar days 2 Medium Structural solution: Between 30-90 calendar days 3 Low Solution The solution shall be included in the release calendar How do get a login to the support tool? You will receive instructions for this as part of your access partner contract.
Volledig artikel weergeven
30-12-2021 10:09 (Bijgewerkt op 30-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 25 Weergaven
Swagger documentation The following swagger pages gives an overview of the endpoint: IAM User endpoint  User endpoint   The user endpoint supports the retrieval of users and to set an identity for a user, the following methods are supported as part of the users endpoint. https://api.youforce.com/iam/v1.0/users GET Allows retrieving a single employee based on employeeId for the tenant specified in the request header. https://api.youforce.com/iam/v1.0/users(employeeId=12345) Supports the following parameter as part of the resource path: employeeId   - The unique id assigned to an employee Returns a   200 OK when successful PATCH Allows to update or set an identity for a specific user based on employeeId for the tenant specified in the request header. https://api.youforce.com/iam/v1.0/users(employeeId=12345)/identity Supports the following parameters as part of its request body: id - Ping Id of the employee which is to be used for SSO { "id": "xxxxxx" } Returns a   204 No content   when successful Visibility of the change in Youforce portal Please note that updating the identity through this endpoint will update the identity in the Youforce authentication system will NOT show the values in Youforce portal Our authentication system is not running on the same service as the portal UI. The synchronization is just one way: Changes done in the authentication system direct will not reflect in the Youforce portal UI Changes done in this UI will reflect in the authentication system This will be addressed in future, when we merge the two services. Datamapping Parameters Description Example Data type employeeId The unique id assigned to the employee by the HR Core 12345 string id User id of the employee used in the Youforce authentication system c7e230db-2a7f-4ef0-ad1d-9d30e7d94a2f string sourceId Username of the user in the Youforce portal XX123456 string identityId UPN/Identity in the customer authentication system that takes care of authentication user@customer.com string
Volledig artikel weergeven
30-12-2021 15:26 (Bijgewerkt op 30-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 22 Weergaven
  Swagger documentation The following swagger pages gives an overview of the endpoint: IAM endpoints    Filters Person endpoint The person endpoint supports the following query string parameters Parameter Description from and to   Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) person records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/persons? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of person records filtered based on the   validFrom   and   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/persons?validFrom=2020-11-07 validUntil Returns a list of person records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date     Employee endpoint The employee endpoint supports the following query string parameters Parameter Description personCode    Returns a list of employee records filtered by   personId https://api.youforce.com/IAM/v1.0/employees?personCode=191166 personId Returns a list of employee records filtered by   personId https://api.youforce.com/IAM/v1.0/employees?personId=191166   organizationUnit Returns a list of all employee records filtered by organizationUnit   id https://api.youforce.com/IAM/v1.0/employees? organizationUnit=13612345 from  and   to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) employee records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/employees? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of employee records filtered based on the   validFrom   and   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/employees?validFrom=2020-11-07 validUntil Returns a list of employee records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date   Employment endpoint The employee endpoint supports the following query string parameters Parameter Description personCode   Returns a list of employment records filtered by   personId https://api.youforce.com/IAM/v1.0/employments?personCode=191166 personId Returns a list of employment records filtered by   personId https://api.youforce.com/IAM/v1.0/employments?personId=191166 organizationUnit Returns a list of all employment records filtered by organizationUnit   id https://api.youforce.com/IAM/v1.0/employments? organizationUnit=13612345   from  and   to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) employment records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/employments? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of employment records filtered based on the   validFrom   and   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/employments?validFrom=2020-10-01 validUntil Returns a list of employment records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date   Assignment endpoint The assignments endpoint supports the following query string parameters   Parameter Description personId Returns a list of assignment records filtered by   personId https://api.youforce.com/IAM/v1.0/assignments?personId=191166 from and to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) assignment records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/assignments? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of assignment records filtered based on the   validFrom Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/assignments?validFrom=2020-01-03 validUntil Returns a list of assignment records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date   Organization unit endpoint The organizationUnits endpoint supports the following query string parameters Parameter Description shortName Returns a list of all organizationUnit records filtered by   shortName https://api.youforce.com/IAM/v1.0/organizationUnits?company=1010A from  and   to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) organization unit records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/organizationUnits? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of organizationUnit records filtered based on the   validFrom   and   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/organizationUnits?validFrom=2020-01-01 validUntil Returns a list of organizationUnit records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date   Role assignment endpoint The roleAssignments endpoint supports the following query string parameters     Parameter Description personId Returns a list of all role assignment records filtered by   personId https://api.youforce.com/IAM/v1.0/roleAssignments?personId=1010A shortName Returns a list of all role assignment records filtered by   shortName https://api.youforce.com/IAM/v1.0/roleAssignments?shortName=MGR from and to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) employee records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/roleAssignments? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z   Job profile endpoint The jobProfiles endpoint supports the following query string parameters Parameter Description shortName Returns a list of all jobProfile records filtered by   shortName https://api.youforce.com/IAM/v1.0/jobProfiles?shortName=1010A from and to Date Time stamp filter: Date Time should be in   UTC Format:   YYYY-MM-DDTHH:MM:SS.sssZ Returns (active) jobProfile records that have changed within the provided date-time range. https://api.youforce.com/IAM/v1.0/jobProfiles? from=2020-01-01T09:00:00.000Z&to=2020-01-01T14:00:00.000Z validFrom Returns a list of jobProfile records filtered based on the   validFrom Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date https://api.youforce.com/IAM/v1.0/jobProfiles?validFrom=2020-01-03 validUntil Returns a list of jobProfile records filtered based on the   validUntil Date timestamp format is always according to ISO 8601   YYYY-MM-DD This is a range filter the response will contain records from the defined date until the latest possible date
Volledig artikel weergeven
20-12-2021 15:27 (Bijgewerkt op 30-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 83 Weergaven
This document describes the ‘ UMRA - Visma Raet IAM API’ -connector. This connector has been built on top of the Visma Raet IAM API.
Volledig artikel weergeven
23-12-2021 15:52 (Bijgewerkt op 23-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 19 Weergaven
This document described the ‘ Ubeeo ATS - Visma Raet Learning API’ -connector. This connector has been built on top of the Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:53
  • 0 Antwoorden
  • 0 kudos
  • 13 Weergaven
This document describes the ‘ IAM3 - Visma Raet IAM API’ -connector. This connector has been built on top of the Visma Raet IAM API.
Volledig artikel weergeven
23-12-2021 15:50
  • 0 Antwoorden
  • 0 kudos
  • 9 Weergaven
This document described the ‘ HelloID - Visma Raet IAM API’ -connector. This connector has been built on top of the Visma Raet IAM API.
Volledig artikel weergeven
23-12-2021 15:49
  • 0 Antwoorden
  • 0 kudos
  • 9 Weergaven
Dit document beschrijft de ‘ProActive  - Visma Raet IAM API’ -connector. Een koppeling gebaseerd op de Visma Raet IAM API.
Volledig artikel weergeven
23-12-2021 15:48
  • 0 Antwoorden
  • 0 kudos
  • 11 Weergaven
Dit document beschrijft de ‘ PlusPort - Visma Raet Learning API’ -connector. Een koppeling gebaseerd op de Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:47
  • 0 Antwoorden
  • 0 kudos
  • 14 Weergaven
Dit document beschrijft de ‘Viadesk  - Visma Raet IAM API’ -connector. Een koppeling gebaseerd op de Visma Raet IAM API.
Volledig artikel weergeven
23-12-2021 15:45
  • 0 Antwoorden
  • 0 kudos
  • 10 Weergaven
This document described the ‘ mijnLMS - Visma Raet Learning API’ -connector. This connector has been built on top of the Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:44
  • 0 Antwoorden
  • 0 kudos
  • 10 Weergaven
This document describes the ‘ De leerrekening (EduBookers) - Visma Raet Learning API’  - connector. This connector has been built on top of the Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:43
  • 0 Antwoorden
  • 0 kudos
  • 7 Weergaven
Dit document beschrijft de ‘Dialog  - Visma Raet Learning API’ -connector. Een koppeling gebaseerd op de Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:42
  • 0 Antwoorden
  • 0 kudos
  • 16 Weergaven
This document describes the   ‘Office Travel App - Visma Raet Learning API’  - connector. This connector has been built on top of the Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:40
  • 0 Antwoorden
  • 0 kudos
  • 10 Weergaven
Dit document beschrijft de ‘AppicalNow  - Visma|Raet Learning API’ -connector. Een koppeling gebaseerd op de Visma Raet Learning API.
Volledig artikel weergeven
23-12-2021 15:39
  • 0 Antwoorden
  • 0 kudos
  • 9 Weergaven
Swagger documentation The following swagger pages gives an overview of the endpoint: SIVI endpoints    Endpoint Verzuimmeldingen The endpoint /verzuimmeldingen will return all generated sick leave messages within a specific tenant / client; strictly corresponded with the Dutch standard of sivi.org. The structure of the XML message is fully in line with the XSD version of Verzuimmelding 2020. Currently we’re not able to return every single field with values. For a detailed data mapping overview, click here.   Full load : GET /verzuimmeldingen To fetch the total list of messages corresponding to a client number the endpoint Verzuimmeldingen can be used without using any additional (filter) parameters. https://api.raet.com/sivi/verzuimeldingen Incremental load : GET /verzuimmeldingen?ChangedAfter=20210402&ChangedUntil=20210404 By executing the parameters ChangedAfter - ChangedUntil the API will only expose the available SIVI messages within the specified timerange. In the below example an API consumer would like to retrieve only the messages between the 2nd of April 2021 and 4th of April 2021.   https://api.raet.com/sivi/verzuimeldingen?ChangedAfter=20210402&ChangedUntil=20210404 Example date-time format : changedAfter - 2020-08-21T00:00:00.000Z changedUntil - 2020-08-21T12:01:46.077Z   Mappings A table with all the corresponding property mappings for the Verzuimmeldingen endpoint can be found here. Pagination of the result set To reduce the load of an endpoint each endpoint supports paging. In case the results of an endpoint contain more than 100 records, the results set will end with a ‘nextLink tag’. The nextLink indicates that there are more pages to load. If there is no nextLink at the end of the page, this means that it’s the last page of the result set.
Volledig artikel weergeven
22-12-2021 12:53 (Bijgewerkt op 22-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 40 Weergaven
  Domain model   Field mapping Verzuimmeldingen The endpoint   /verzuimmeldingen   exposes all the corresponding personal, contract & sick leave details of an employee. ALGEMEEN (R) DESCRIPTION XML-TAG R / O EXAMPLE BO4 ONLINE Soort bericht + versienummer BrCd R 00100 Configuration API Versienummer bericht, code VnrBrCd R 00008 Configuration API Aanmaakdatum bericht AandatBr R 2021-03-31 System Date Aanmaaktijd bericht AantijdBr R 13:06:55 System Time Identificatie inzender IdInzndr R Visma - Raet NA Gebruikt softwarepakket GebrSwPakket R BO4 System Data Identificatie ontvanger IdOntvngr R 101 Configuration API Bericht referentienummer Berrefnr R 20210331 T1306559722624Z System Data Test J/N TestJN R N System Data Ontvangstbevestiging gewenst J/N OntvngstbevJN R N System Data ADMINISTRATIEKANTOOR (O) DESCRIPTION XML-TAG R / O EXAMPLE BO4 ONLINE Handelsnaam organisatie HndlsnmOrg R NA   Inschrijvingsnummer Kamer van Koophandel InschrijvingsnrKvK O NA   Vestigingsnummer Vestigingsnr Handelsregister O NA   WERKGEVER (R)         Handelsnaam organisatie HndlsnmOrg R Bogé regressiebestand Opdrachtgever Inschrijvingsnummer Kamer van Koophandel InschrijvingsnrKvK O NA   Vestigingsnummer Vestigingsnr Handelsregister O NA   Identificatie werkgever bij Arbo-dienst IdWrkgvrArbdnst R 105 Configuration API Aansluitnummer gegevensuitwisseling Arbodienst AansltnrGeguitwlng Arbdnst R 6431 Configuration API/To be received from Arbo Identificatie werkgever bij UWV IdWrkgvrUWV O NA   Loonheffingennummer Lhnr O NA   Indicatie eigenrisicodrager voor de WGA IndERDWGA O NA   Indicatie eigenrisicodrager voor de ZW IndERDZW O NA   STRAATADRES NEDERLAND StrAdrNl O     Soort adres, code SrtAdrsCd R 01   Ingangsdatum Ingdat O NA   Einddatum Enddat O NA   Postcode Pc R 3821 BB   Woonplaatsnaam Wnpl R Plotterweg   Straatnaam StraatLang O NA   Huisnummer Huisnr R 38   Huisnummertoevoeging HuisToev O A   POSTBUSADRES NEDERLAND (O) PbadrsNl O     Ingangsdatum Ingdat O NA   Einddatum Enddat O NA   Postcode Pc R NA   Woonplaatsnaam Wnpl R NA   Postbusnummer Pbnr R NA   COMMUNICATIE (O) Soort communicatie, code SrtComCd R NA   Nummer/adres communicatie NrCom R NA   CONTACTPERSOON (O) Identificatie Werknemer IdWrknmr O NA   Personeelsnummer Persnr O NA   Achternaam /Achternamen Achternaam R NA   Voorletters Voorl O NA   Roepnaam Roepnaam O NA   Geslachtsaanduiding, code GslchtCd O NA   Rol contactpersoon, code RolCntprsnCd R NA   COMMUNICATIE (R) Soort communicatie, code SrtComCd R NA   Nummer/adres communicatie NrCom R NA   WERKNEMER (R) Ingangsdatum mutatie IngdatMut O NA   Burgerservicenummer SofiNr O NA   Geboortedatum Gebdat R 1990-03-20 P00321 Overlijdensdatum Overldat O 2013-11-20 P01005- Datum overlijden Significant deel van de achternaam SignNm R Hoffman P00301 - Geboortenaam Voorletters Voorl R M P00303 - Voorletters Voorvoegsels Voorv O de P00302 - Geboortenaam-voorvoegsels Roepnaam Roepnaam O Marcel P01003 - Roepnaam Titulatuur voor de naam TitVNm O Doctor P00305 - Titulatuur voor de naam Titulatuur achter de naam TitANm O NA P03937 - Titulatuur achter de naam Naamvoorkeur, code NmvrkrCd R 01 P00304 - Gebruik achternaam Geslachtsaanduiding, code GslchtCd R M P00330 - Geslacht Niveau opleiding, code NivOpldngCd O NA   Identificatie werknemer IdWrknmr R 700066 P01001 - Persoonsnummer Identificatie werknemer oud IdWrknmrOud O NA   BANKREKENING BnkGiro O NA   IBAN Iban O NA   BIC Bic O NA   PARTNER (O) Significant deel van de achternaam SignNm R Maria P00390 - Partner-naam Voorvoegsels Voorv O E P00391 - Partner-voorvoegsels STRAATADRES NEDERLAND (O) Soort adres, code SrtAdrsCd R 01 System Data Soort verpleegadres, code SrtVrplgadrsCd O NA System Data Naam verpleegadres NmVrpladrs O VU Medisch Centrum P01622 - Naam verpleegadres Ingangsdatum Ingdat O 2021-03-03 P01620 - Ingangsdatum verpleegadres Einddatum Enddat O 2021-04-21 P01621 - einddatum verpleegadres Postcode Pc R 3816NR P01626 - verpleegadres Woonplaatsnaam Wnpl R HAARLEM P01627 - verpleegadres Straatnaam StraatLang O Haarlemmerstraat P01623 - Straatnaam verpleegadres Huisnummer Huisnr R 45 P01624 - huisnummer verpleegadres Huisnummertoevoeging HuisToev O B P01625 - huisnummer toe verpleegadres STRAATADRES BUITENLAND (O) Soort adres, code SrtAdrsCd O NA   Soort verpleegadres, code SrtVrplgadrsCd O NA   Naam verpleegadres NmVrpladrs O NA   Ingangsdatum Ingdat O NA   Einddatum Enddat O NA   Locatieomschrijving buitenland LocomsBtl O NA   Postcode buitenland PcBtl O NA   Woonplaatsnaam buitenland WnplBtl R NA   Regionaam buitenland RegBtl O NA   Land, code LandCd R NA   Landnaam Landnm O NA   Straatnaam StraatLang O NA   Huisnummer buitenland HuisnrBtl R NA   COMMUNICATION (O) Soort communicatie, code SrtComCd R 05 System Data Nummer/adres communicatie NrCom R marcel.h@icici.com marcel.h@gmail.com 0612399001 0610922334 P01035 - E-mail adres werk P01034 - E-mail adres prive P01036 - Telefoonnr mobiel P01037 - Telefoonnr werk DIENSTVERBAND (R) Ingangsdatum mutatie IngdatMut O NA   Identificatie dienstverband IdDnstvbnd R 1 System Data Identificatie dienstverband oud IdDnstvbndOud O NA System Data Ingangsdatum Ingdat R 2021-01-01 P00322 - Datum in dienst Einddatum Enddat O 9999-12-31 P00830 - Datum uit dienst Reden einde dienstverband, code RdEndDnstvbndCd O 01 System Data Personeelsnummer PersNr O 700060 P01001 - Persoonsnummer Personeelsnummer oud PersNrOud O NA   Contractnummer bij Arbo-dienst CntrnrArbdnst O NA System Data Soort dienstverband, code SrtDnstvbndCd O NA P01102 - Soort arbeidsrelatie Functiecode Fnctcd O 3002 P01107 - Primaire functie Naam functie NmFnct O accountant P01107 - Primaire functie Code fase indeling F&Z FsIndFZ O NA   Naam organisatie-eenheid NmOrgeenh O API Public Support 7 Sickness P01106 - Hierarchische org. eenheid Organisatie-eenheid, code OrgeenhCd R 1882 P01106 - Hierarchische org. eenheid Onderdeel van organisatieeenheid, code OndOrgeenhCd O 801   Onderdeel van organisatie-eenheid, naam OndOrgeenhCdNm O Algemene ondersteuning   Postcode standplaats PcStandplts O NA   Verdeling, code VrdlngCd O NA   Code contract onbepaalde / bepaalde tijd CdBepTd O O/B P08259 - Code contract Aantal contracturen per week AantCtrcturenPWk O 36.0 P01109 - Uren per week Soort variabele werktijden, code SrtVarWrktdCd O NA   Aantal loonwachtdagen AantLnwchtdgn O NA   Percentage loondoorbetaling PrcLndrbtng O NA   ARBEIDSRELATIE (O) Identificatie arbeidsrelatie IdArbeidsrelatie R NA   Identificatie arbeidsrelatie oud IdArbeidsrelatieOud O NA   Personeelsnummer PersNr O NA   Personeelsnummer oud PersNrOud O NA   Ingangsdatum Ingdat R NA   Ingangsdatum mutatie IngdatMut O NA   Einddatum Enddat O NA   Aantal contracturen per week AantCtrcturenPWk R NA   KOSTENPLAATS (O) Ingangsdatum Ingdat O NA   Ingangsdatum mutatie IngdatMut O NA   Einddatum Enddat O NA   Naam kostenplaats NmKostenplaats R NA   Kostenplaats, code KostenplaatsCd R NA   Onderdeel van kostenplaats, code OndKostenplaatsCd O NA   Onderdeel van kostenplaats, naam OndKosten plaatsNm O NA   VERZUIM (R) Verwerking, code VrwrkCd R 01 System Data Ingangsdatum mutatie verzuim IngdatMutVrzm R 2021-03-01 System Data Ingangsdatum mutatie verzuim oud IngdatMutVrzmOud O 2021-02-21 System Data Verzuimgeval identificatie VrzmgvlId R 700060 1 926 Combination of Personeelsnummer + Identificatie dienstverband + Sickness ID Verzuimgeval identificatie oud VrzmgvlIdOud O NA   Verzuimgeval volgnummer melding VrzmgvlVnrMld R 2 System Data Einde verzuim J/N EndVrzmJN R J   Datum verzuimmelding werkgever DatVrzmWrkgvr O 2021-11-21 P01603 - Datum ziekmelding Datum eerste verzuimdag DatEerstVrzmdg R 2021-07-31 P01600 - Datum eerste ao-dag Datum eerste verzuimdag oud DatEerstVrzmdgOud O 2021-04-11   Datum hersteld DatHrstld O 2021-03-20 P01606 - Datum herstel Datum hersteld werkgever DatHrstldWrkgvr O NA   Percentage verzuim PrcVrzm R 80 P01642 - ziekte percentage Bijzondere reden start verzuim, code BijzRdnStartVrzmCd O NA   Oorzaak verzuim, code OorzkVrzmCd R 99   Vangnetgeval J/N VngntJN R J P01645 - Soort vangnetgeval Reden einde verzuim, code RdnEndVrzmCd O 01   WAZO, code WAZOCd O 01   Nummer uitkering bedrijfsvereniging NrUitkBdrver O NA   Percentage arbeidstherapie PrcArbther O NA   CONTACTPERSOON (O) Identificatie Werknemer IdWrknmr O 700066   Personeelsnummer Persnr O 700066 Personeelsnummer of the Contact person Achternaam /Achternamen Achternaam R Veltman   Voorletters Voorl O A   Roepnaam Roepnaam O Marcel   Geslachtsaanduiding, code GslchtCd O V   Rol contactpersoon, code RolCntprsnCd R 01   COMMUNICATIE (R) Soort communicatie, code SrtComCd R 06   Nummer/adres communicatie NrCom R alisha.veltman@raet.com   ACTIE (O) Actie, code ActieCd R NA   VRIJE TEKST (O) Vrije tekst VrijeTekst R NA   CONTACTPERSOON (O) werkgever - werknemer - dienstverband - CONTACTPERSOON Identificatie Werknemer IdWrknmr O 700066   Personeelsnummer Persnr O 700066   Achternaam /Achternamen Achternaam R Veltman   Voorletters Voorl O A   Roepnaam Roepnaam O Marcel   Geslachtsaanduiding, code GslchtCd O V   Rol contactpersoon, code RolCntprsnCd R 01   COMMUNICATIE (R) werkgever - werknemer - dienstverband - contactpersoon - COMMUNICATIE Soort communicatie, code SrtComCd R 08   Nummer/adres communicatie NrCom R 0622345978  
Volledig artikel weergeven
21-12-2021 17:15 (Bijgewerkt op 22-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 44 Weergaven
Swagger documentation The following swagger pages gives an overview of the endpoint: Learning API  Pagination of the result set To reduce the load of an endpoint each endpoint supports paging. If the results of an endpoint contain more than 500 records, the results set will end with a   nextLink tag. The nextLink indicates that there are more pages to load. If there is no nextLink at the end of the page, it means that it’s the last page of the result set. The default value is 500 records, but it is possible to use less than that.   Delete a record After a record is deleted in the core system, the API will return the record with his   id   and the flag   isDelete = true. This delete means that the whole record including all version are delete. For example { "id": "907624", "isDeleted": true, "shortName": "907624" }  
Volledig artikel weergeven
21-12-2021 15:22 (Bijgewerkt op 21-12-2021)
  • 0 Antwoorden
  • 0 kudos
  • 24 Weergaven