LOloket
Preboarding trajectory

Add a preboarding trajectory

Activity name : <a href="https://developer.loket.nl/Activities/PostPreboardingTrajectoryByConceptEmployeeId" target="_blank">PostPreboardingTrajectoryByConceptEmployeeId</a>

post/v2/providers/employers/conceptemployees/{conceptEmployeeId}/preboardingtrajectory

Request

  • Base URL
    https://api.loket.nl
  • URL
    https://api.loket.nl/v2/providers/employers/conceptemployees/{conceptEmployeeId}/preboardingtrajectory
  • Auth
    none required

Path parameters

conceptEmployeeIdstring uuid required

The unique identifier of the concept employee

Headers

Authorizationstring required
Example:Bearer <TOKEN>

A valid Bearer token for authorizing the request.

Acceptstring required
Example:application/json;version=2018-01-01

The accept header is used to influence what type of output is returned and in most cases the version of the output

Request body

fragmentsstring nullable

JSON string containing the fragments the conceptemployee should provide in the preboarding flow

Example request

{
  "fragments": "[\n  \"idBewijs\",\n  \"persoonsGegevens\"\n]\n"
}

Response

Created

Example response

{
  "version": {
    "resourceVersion": "2018-12-31"
  },
  "messages": [
    {
      "type": "Warning",
      "description": "<some warning>",
      "id": "904d6856-6034-4624-bcbc-886188c115c5",
      "code": 12
    }
  ],
  "content": {
    "id": "b14acd0d-75d7-4fc8-8b22-4a3924585cab",
    "status": "open",
    "dateLastModification": "2022-04-12",
    "clientName": "ESS",
    "fragments": "[\n  \"idBewijs\",\n  \"persoonsGegevens\"\n]\n"
  }
}

Changes

No recorded changes to this operation across all 6 revisions of this API.